R12 Implementation Recommendations For Germany (February 2010) E15627-01

Oracle E-Business Suite
Implementation Recommendations for Germany

Release 12
Part No. E15627-01
February 2010
Oracle E-Business Suite Implementation Recommendations for Germany, Release 12

Part No. E15627-01
Copyright 2009, 2010, Oracle and/or its affiliates. All rights reserved.
Primary Author: Oracle Germany Consulting
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf
of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication,
disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the
applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle
USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications which may
create a risk of personal injury. If you use this software in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of
this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software in dangerous applications.
This software and documentation may provide access to or information on content, products and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third party content, products and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third
party content, products or services.

Contents
Send Us Your Comments

Preface
1
Introduction
Overview................................................................................................................................... 1-1
Setup Related Recommendations and Considerations

Introduction............................................................................................................................... 2-1
System Administration............................................................................................................. 2-1
General Ledger.......................................................................................................................... 2-2
Ledger Architecture................................................................................................................... 2-3
MultiOrg Access Control.......................................................................................................... 2-5
Payables..................................................................................................................................... 2-9
Receivables.............................................................................................................................. 2-11
Banking Model........................................................................................................................ 2-16
Payments ................................................................................................................................. 2-28
Collections .............................................................................................................................. 2-35
Assets....................................................................................................................................... 2-36
EBusiness Tax ......................................................................................................................... 2-38
Process Related Recommendations and Considerations

Over All..................................................................................................................................... 3-1
General Ledger.......................................................................................................................... 3-1
Payables..................................................................................................................................... 3-4
Receivables................................................................................................................................ 3-5
iii
Cross Payables/Receivables...................................................................................................... 3-9

Payments.................................................................................................................................. 3-10
Assets....................................................................................................................................... 3-17
New Localizations R12............................................................................................................ 3-18
Audit Trail
Define Tables to be Audited..................................................................................................... 4-1
Functional Setup...................................................................................................................... 4-11
Audit Trail Report .................................................................................................................. 4-12
Reconciliation Process
Cash Management..................................................................................................................... 5-1
Payables..................................................................................................................................... 5-4
Receivables.............................................................................................................................. 5-10
Assets....................................................................................................................................... 5-18
General Ledger........................................................................................................................ 5-23
Reconciliation Reports
Cash Management..................................................................................................................... 6-1
Payables..................................................................................................................................... 6-5
Receivables.............................................................................................................................. 6-16
Assets....................................................................................................................................... 6-28
General Ledger........................................................................................................................ 6-57
VAT Reconciliation................................................................................................................. 6-71
Index
iv

Send Us Your Comments
Oracle E-Business Suite Implementation Recommendations for Germany, Release 12
Part No. E15627-01
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
Are the implementation steps correct and complete?

Did you understand the context of the procedures?
Did you find any errors in the information?
Does the structure of the information help you with your tasks?
Do you need different information or graphics? If so, where, and in what format?
Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.

Preface
Intended Audience
Welcome to Release 12 of the Oracle E-Business Suite Implementation Recommendations for
Germany.
It is intended for a customer in Germany.
See Related Information Sources on page viii for more Oracle E-Business Suite product
information.
Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call
Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle
technical issues and provide customer support according to the Oracle service request
process. Information about TRS is available at
http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is
available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible
to all users, including users that are disabled. To that end, our documentation includes
features that make information available to users of assistive technology. This
documentation is available in HTML format, and contains markup to facilitate access by
the disabled community. Accessibility standards will continue to evolve over time, and
Oracle is actively engaged with other market-leading technology vendors to address
technical obstacles so that our documentation can be accessible to all of our customers.
For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.
vii
Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an otherwise
empty line; however, some screen readers may not always read a line of text that
consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.
Structure
1 Introduction
2 Setup Related Recommendations and Considerations
3 Process Related Recommendations and Considerations
4 Audit Trail
5 Reconciliation Process
6 Reconciliation Reports
Related Information Sources

This manual is to be referred in conjunction with Oracle Applications R12 Reference
Manuals of the respective modules.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
viii
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
ix
1
Introduction
Overview
When implementing Oracle E-Business Suite R12 in Germany there are several local
legal requirements and good business practices, which need to be taken into
consideration when implementing the software.
This document reflects project results of current Oracle E-Business Suite R12
implementations in Germany as well as findings during an Oracle internal project to
achieve product certification for the financial modules of the suite.
The following four sections are covered by the document:
Setup
Process
Audit Trail
Reconciliation
Each of the four sections covers the most common Oracle E-Business Suite modules.
The sections will give additional advice on the base and country-specific setup as well
as recommendations for daily business practice. Screen-shots are used to illustrate the
topics where appropriate.
The focus has been set on the following modules:
General Ledger
Payables
Receivables
Payments
Introduction 1-1
Fixed Assets
E-Business Tax
Oracle E-Business Suite Advanced Collections is also mentioned here, as much of the
former Receivables functionality has been moved to Advanced Collections.
This document only gives additional advice on some specific implementation topics for
Germany. Therefore it is strongly recommended also to refer to the existing Oracle
standard documentation e.g. Oracle Implementation and User Guides for further
reference.
1-2 Oracle E-Business Suite Implementation Recommendations for Germany
2
Setup Related Recommendations and
Considerations
Introduction
An IT-Governance framework should be implemented to control the following
procedures:
Definition of Roles and Responsibilities
Assignment of Setup functions to Roles/Responsibilities
Initiate Setup documentation
Update Setup documentation
From an auditing perspective it is crucial, that all setup documentation is created and
maintained properly.
For additional information on how to monitor change of master data, please have a look
at the chapter Audit Trail.
The following section addresses some additional system administration and setup
recommendations, which should be taken into consideration when implementing
Oracle E-Business Suite in Germany.
System Administration
Changing APPS Password
Oracle Applications offers a function to access the data on the table level from the
application by using Diagnostic/Examine from the menu bar.
In order to prevent users from changing table entries using this feature the password of
Setup Related Recommendations and Considerations 2-1
the "Apps" user should be changed from the standard value to a specific password.
This account should be used by the technical support group and/or database
administration only.
It is also recommended to set the profile option: "Utilities: Diagnostics" to No; this will
require the user to enter a password.
Responsibilities
The Oracle E-Business suite offers the possibility to have individual user management
and individual responsibilities to restrict the access to the data a user can see, and to the
functions a specific user has available. These responsibilities can be either attached
directly to a user, or to a role, which is than assigned to a user. When setting up user
management, the implementation team can choose to use either a seeded responsibility
or to create new responsibilities, which can be created to the individual needs. With
roles and responsibilities it is also possible to achieve a segregation of duties.
User Password Changes

The usage of passwords for all users should be set to "expires periodically" after a given
time period or after a defined number of accesses to the system.
Document Sequencing
Document sequencing must be setup. Create the document sequences for all Oracle
Applications modules that are implemented, and assign them to the appropriate
document categories.
It is recommended to setup the document sequences as gapless.
Furthermore, it is recommended to renew the sequence definition and sequence
assignments on a fiscal year basis.
Set the profile option Sequential Numbering to "Always used" in order to be sure, that
no accounting entries are created without a document sequence number.
General Ledger
Accounting Sequencing
To ensure that gapless sequential numbering is assigned to journal entries the
accounting sequencing should be setup.
Accounting sequencing is set up with the option "GL Period Close GL Journal Entry".
With accounting sequences, gapless numbering, and continued numbering can be
achieved.
The initiation for the accounting sequence is done during the accounting event.
Accounting Sequence elements:
Sequence definition
Sequence assignments
should be renewed on a fiscal year basis.
Ledger Architecture
Ledgers
With Oracle E-Business Suite R12, a new ledger architecture has been introduced:
Ledgers can be defined as:
Primary ledger
Secondary ledger
Reporting Ledger
In addition to a secondary ledger, a primary ledger can also have a reporting ledger
assigned.
The primary / secondary ledger architecture is often being used to accommodate
different Accounting Standards in parallel. (e.g. HGB and IFRS).
Reporting ledgers are used to reflect accounting in a different (reporting) currency.
Primary ledgers can be linked to one or more legal entities. For a German
implementation it is mandatory to have a 1:1 relationship between the defined legal
entity and the corresponding primary ledger.
Ledger Sets
In R12, Ledger Sets is a new functionality to create a list of ledgers, which are using the
same:
Accounting Flexfield
Calendar
Ledger Sets can be used for different functions such as:
Journal entry
Recurring journals
Allocations
Period close
Reports
In addition a Data Access Set, with enhanced security options needs to be defined in
order to use Ledger Sets.
Ledger Sets are assigned to a user responsibility by the profile option: GL: Data Access
Set.
MultiOrg Access Control

Setup Overview
Oracle E-Business Suite R12 introduces the MultiOrg Access Control (MOAC) feature,
which enables a user to enter transaction and master data for different operating units
without changing their responsibility.
Setting up or using MOAC is optional; the former MultiOrg access via separate
responsibilities is still in place and can continue to be used.
If centralized functions are required, for example a shared service center for Payables,
the use of MOAC will provide the required functionality to do so.
Security Profile
A security profile is a list of operating units, which can be assigned on user or
responsibility level by using the appropriate profile option.
After defining your Security Profile (in HR),run the concurrent request:
Security List Maintenance
to derive a complete list of your organizations when using MOAC.
Profile Options
The MOAC Architecture uses the following profile options, which can be set on
different levels (including user) :
MO: Security Profile

Here the security profile is assigned
MO: Default Operating

Unit If a security profile has been assigned containing more than one organization,
the defaulting organization will be derived based on this profile option.
Accounting Setup Manager: Subledger Accounting Options

Regarding the transfer of transactions from the Subledgers to the General Ledger, there
are three summarization options:
No summarization
Summarized by GL-Date Period
Summarized by GL Period
In order to have a complete drill down from the General Ledger to the Subledger select
the "No summarization" option.
It is also recommended to set the parameter "Post in GL" to "Yes" to get the process of
accounting completed at once.
This task has to be performed for every module within Financials, which is part of the
implementation.
Furthermore this setup is required to get complete General Ledger Journals. This also
facilitates compliance with the regulation GDPdU
Accounting Setup Manager: Suspense Accounting

It is recommended not to setup Suspense Accounting. This will prevent users from
posting unbalanced journals.
Third Party Control Accounts

Restrict the access to certain Accounts for manual journal entries from the General
Ledger responsibility in order to ensure that only a subledger application can enter
journals to these accounts and to simplify reconciliation. Third Party Control accounts
could be:
Liability account, used in AP for transactions
Receivables Account, used in AR for transactions
Asset Clearing Account
Web ADI Journal Entries

It is recommended to use the option "Automatically Submit Journal Import" due to the
fact that the user who entered the transaction isn't necessarily the same person who
posted the journal entry into GL.
Oracle considers Web ADI to be a Subledger. Consequently "Third Party Control
Accounts" can be used for transaction generation as well. If posting to Third Party
Control Accounts by Web ADI is not wanted this has to be secured by organizational
means.
Payables
Setup Payables Options (in extracts)
Payables System Setup
It is suggested to setup the following values using
(Resp) Payables (M) Setup/Options/ Payables System Setup
Description
Value
Supplier Number
Automatic
Type
Numeric Terms
Date Basis
Invoice
Payables Options - Discount

To setup this option Navigate to Payables Options, Tab: Accounting Options
Description
Value
Discount Method
System Account
Prorate Expense
Prorate Tax
There are three different discount methods available:

1. Prorate Tax
This option is used for creating a tax correction based on the discount taken, and to
credit the remaining discount amount to the "discount taken" account. In that case there
is no automatic transfer of reduced costs to Fixed Assets paid invoices available.
2. Prorate Expense
This option credits prorata all expense accounts and also makes corrections to the VAT.
This option brings the reduced costs for Fixed Assets paid invoices to the Mass
Additions for Fixed Assets if the accounting for the invoice lines is made to the Fixed
Assets interims account. There will be no specific accounting for discount taken.
3. System Account
This option credits all discounts to the system "discount taken" account. No automated
tax correction will be provided, when discount has been taken.
In a German implementation it is recommended to use one of the "Prorate"-options to
create discount driven tax reduction. But the "Always Take Discount" option in the
supplier setup (Invoice Management) should not be enabled.
Payables Options Currency
It is suggested to setup following values using
Payables Options, Tab: Currency
Description
Value
Use Multiple Currencies
Yes
Define the Accounts for
Realized Gains
Account for Realized Gains
Realized Loss
Account for Realized Loss
Rounding
Account for Rounding
Payables Options Invoices

It is suggested to setup the following values using
Payables Options, Tab: Invoices
Description
Value
GL-Date Basis
Invoice Date
Payables Options Interest

It is suggested to setup following values using
Payables Options, Tab: Interests
Description
Value
Allow Interest Invoices
No
Payables Options Payment

The Exclude Tax From Discount Calculation option specifies whether Payables
subtracts the tax amount from the invoice amount when it calculates the invoice
amount applicable to discount.
It is suggested not to enable this option.
Payables Options, Tab: Payments
Description
Value
Exclude Tax from Discount Calculation
No
Receivables
System Profile Options
To setup these options, navigate to System Profile Options within the System
Administrator Responsibility
These system profile options should be set up as follows:

Profile Option
Value
AR: Application GL Default
Later of Current date, Receipt and Invoice GL

date
Choose this value to use either the receipt GL
date or the invoice GL date, whichever is later,
as the default GL date for your receipt
applications. This is the default value.
AR: Cash - Allow Actions
Yes
AR: Change Customer on Transaction
No
AR: Enable Journal Balance Check
Yes
AR: GL Transfer Balance Test
Yes
AR: Mask Bank Account Numbers
Mask - First Four Digits Visible
AR: Override Adjustment Activity Account

Option
Yes
AR: Update Due Date
Yes
AR: Use Invoice Accounting For Credit

Memos
Yes
HZ: Change Party Name
No
System Options
To setup System Options navigate to System Options within the Receivables Manager
Responsibility
(Resp) Receivables (M) Setup/Options/ Reeivables System Options System Options, Tab:
Accounting:
These receivables system options should be set up as follows:
Form Field
Value
Automatic Journal Import
Yes
Define Accounts for:
Exchange rate gains account
Realized Gains
Exchange rate losses account
Realized Losses
Default tax account
Tax
Rounding errors during application of cross

currency receipts account
Cross Currency Rounding
Important: Once header level rounding is
Optionally define Accounts for:
active, the setting cannot be turned off!
Header Rounding
Unallocated Revenue
System Options, Tab: Transactions and Customers:

Form Field
Value
Allow change to printed transactions
No
Allow transaction deletion
No
Allow payment of unrelated transactions
Yes
Document number generation level
When Completed
To be in accordance with German GDPdU regulations, the system option "Allow

changes to printed transactions" should be set to "No". If necessary, changes should
always be done by using credit memos, adjustments etc. rather than changing a printed
transaction.
Also, the system option "Allow transaction deletion" should be set to "No". This is
necessary to prevent gaps in the document sequence for Receivables transactions.
Credit memos or adjustments are the tools to use to close (reverse) an unwanted
transaction. System Options, Tab: Miscellaneous:
System Options, Tab: Miscellaneous:
Form Field
Value
Discount basis Application Rule Set
Invoice amount
Require billing location for receipts
Yes
Discount on partial payment
Yes
Chargeback due date
Open invoice due date
Source of territory
None
Application Rule Set
Prorate all
Setup VAT for adjustments when applying adjustments and discounts

Receivables Activities are required to make sure that correct VAT accounting entries
due to adjustments and discounts are created automatically:
Receivable activities for adjustments (option 1)
Type
Adjustment
GL Account Source
Tax Code on Invoice
Tax Rate Source Code
Invoice
Allocate the net portion using the Expense/Revenue accounts specified by the tax rate
code on the invoice. Distribute the tax amount to the tax accounts specified by the tax
rate code on the invoice.
Receivable activities for adjustments (option 2)
Type
Adjustment
GL Account Source
Activity GL Account
Invoice
Allocate the expense or revenue to the General Ledger account that is specified for this
Receivables Activity. Distribute the tax amount to the tax accounts specified by the tax
rate code on the invoice.
Receivable Activities for Adjustments (option 3)
Type
Adjustment
GL Account Source
Revenue on Invoice
Invoice
Allocate the expense or revenue net of any tax to the revenue account(s) specified on the
invoice. Distribute the tax amount to the tax accounts specified by the tax rate code on
the invoice.
Receivable Activities for Discount Type
Type
Adjustment
GL Account Source
Tax Code on Invoice
Invoice
These Receivables Activities for earned and unearned discounts have to be referenced
when defining receipt method accounts and will be used for account derivation when
discounts are calculated during the receipt application process.
Therefore, the corresponding accounts have to be defined when the respective tax rates
are defined:
Customer setup considerations

The Value Added Tax identification number (Umsatzsteuer-Identifikations-Nummer:
UID) in the Tax Profile on customer account level under "Tax Registrations" must be
defined. Select the tax regime code of the customer's home country and enter the UID.
Set the Effective Date From and save.
Additionally set "Associated Fiscal classifications" under the Fiscal Classification Code
to "Registered" if the customer has a UID assigned.
Banking Model
Banking Setup - Overview
Since the release of Ebusiness Suite R12, banking setup is part of the Trading
Community Architecture (TCA). Bank accounts can be defined as external and internal.
External bank accounts are part of the setup process within suppliers / customers in the
corresponding Payables / Receivables Financials application modules. Internal and
external bank accounts setup prerequisites are:
Banks
Bank branches
Banks and bank branches are shared between legal entities, suppliers and customers.
Internal bank accounts need additional setup as:
Detailed bank information
Owner information and modules
Detailed bank accounting information
Payable documents setup.
The Cash Management module owns the internal bank accounts.

In order to perform payments, the following steps need to be performed:
Setup an external bank account
Assign an external bank account to a supplier
Setup an internal bank account.
Define a bank
In order to define a bank, use the Cash Management responsibility and navigate to:
(Resp) Cash Management (M) Setup/Banks
The "Manage Banks and Branches" page will be found here. When clicking the Banks
tab, all necessary fields will be displayed to start with the bank definition:
Click on the "Create" button. On the next page additional bank information can be
entered:
Country and bank name are mandatory fields.

After saving the information the bank address page will be shown. Bank address fields
are not mandatory. Click "Finish" to complete bank definition.
Define a bank branch

In order to define a bank branch use the Cash Management responsibility and navigate
to:
The "Manage Banks and Branches" page will be found here.
Navigate to the "Bank" tab and enter the previously defined bank (by name).
The page will show the Create Branch button.
Search for the bank defined in the previous section:
Click the "Create Branch" button to start the bank branch definition.
The following popup is displayed:
By pressing the "Continue" button the bank branch details form will be opened:
Enter the mandatory fields:
Branch Name
Mandatory field. Branch names are only unique within the bank / bank branch
combination.
Branch Number
In some countries this field is mandatory and a validation is done on the number being
entered (France, Switzerland). For German payment format this field must be entered
with the bank code (BLZ).
BIC Code
For using SEPA Payments the BIC Code is mandatory
Branch Type
For using SEPA Payments the value SWIFT is required. For German standard payment
format the value OTHER is correct.
After saving the information the bank branch address page will be shown. Bank branch
address fields are not mandatory. Click finish to complete bank branch definition.
Create an internal bank account

Within Cash Management responsibility under navigate to:
The "Manage Banks and Branches" page is displayed.
Clicking the "Bank Branch" tab and entering the previously defined bank branch (by
name) will show the create account button.
The following form is shown:
Click the "Create" button, and the following information will be derived:
Click on "Continue", and the legal entity selector page opens up.
When the "Bank Account Owner" field is opened, the system will allow selection of a
legal entity:
Select the relevant legal entity, which owns the bank account.
Note: If the legal entity cannot be derived, the cash management
security wizard should be used in user management to create the

correct grants for this setup activity.
Determine the purpose of the bank account. Typically in a Financials implementation,

Payables and receivables are using the internal bank account.
Click on "Next".
Important: Note that the country of the bank determines the validation
of the bank account number for many countries.

It is recommended to enable "Multiple Currencies Allowed", even
when it is currently intended to use only one currency. This will allow
for payments in foreign currency.
Account name: this name must be unique within the bank branch only.
It can be up to 100 characters long.
If automatic bank statement sequencing in Cash Management is used, it
is recommended to restrict the bank account name definition to a
maximum 30 characters in length. It is also suggested that bank account
names are uniquely defined within a ledger to derive correct bank
account sequences. Be aware that bank account names are
case-sensitive.
Check digits
For German payment formats this field can be left empty. For some other countries (e.g.
France), this check digit field is mandatory, as it is a component of the total account
number (French RIB).
IBAN code
For SEPA payments, the IBAN (International Bank Account Number) code is necessary.
There is also a validation on this field. If it is planned to use SEPA in the future, it is
recommended to setup the IBAN number from the start.
Click "Save and Next".
General Controls/Cash Clearing

Cash clearing can be used to show payment transactions in transit on a different
account. If it is required to track clearing by Payment Document it is recommended to
use Advanced Derivation Rules (Subledger Accounting).
There are many other options for the bank account, which affect the payment process;
refer to the Cash Management manual for their explanations.
Click on "Save and Next" to continue.
Click on "Add Organization Access" and the following page is displayed:
Select the operating unit and "Continue".
The last step can be repeated to allow the usage of the bank account within several
operating units within the same ledger.
After pressing "Finish", the bank account definition has been completed.
Manage Payment Documents

Within Cash Management responsibility under navigate: Setup>Bank Accounts
The "Manage Bank Accounts" page can be found. Executing a simple search to derive
the previously defined bank account will offer the "Manage Payment Documents"
Button, which can be clicked after checking the relevant Bank account:
The Manage Payments Documents page opens:
Click on "Create".
Enter a name for the payment document:
Create a supplier bank account

Supplier bank accounts are defined during the setup of a supplier.
Within Payables responsibility navigate to: Suppliers / Entry and perform a search for
an existing supplier.
Navigate to "Banking Details" from the menu at the left side of the screen.
Change the account assignment level to "Site", and click "Go"

Click on "Create".
Enter bank, bank branch and bank account details as follows:
Click "Apply".
After searching the supplier again the following details can be found within the bank
account details form:
Create a Customer Bank Account

Creating a customer bank account can be done on account level as well as on site-level
within the functions offered on the "Payment Details"-Tab.
The form offers to define a complete new external bank account including a definition
of bank and bank branches.
If bank or bank and branch are already defined they can be selected, and a new bank
account will be added to the customer.
To create the correct format, the direct debit bank instruction has to be set to the
appropriate value, which has been contractually agreed with the customer.
Payments
Payments Setup - Overview
Oracle E-Business Suite introduces with R12 a new Module: "Payments", which
interacts with:
Oracle Receivables
Oracle Payables
Oracle Cash Management
Oracle Loans
Setup to be done can be divided in three areas:
Shared Setup
Funds Disbursement Setup
Funds Capturing Setup
The majority of the objects are delivered as seeded values with the product. The
following payments setup is focusing on the key elements and how to set them up.
Shared Payments Setup

Generic setup has to be done which is being used in both flows:
The necessary steps to perform payment functions are:
Transmission Configuration
Payment Systems
Transmission Configuration
There are several transmission mechanisms, which can be used:
Within the Transmission configuration the following setup is performed:
Payment Systems
German payment formats can be found in the "German Payment System" as well as in
the "Global Payment System".
To use a payment system, a payment system account needs to be set up.
The main payment formats can be found as seeded data:
Funds Disbursement Setup

Funds disbursement setup is used with the focus on outbound payments.
Funds disbursement setups:
Payment Methods
Payment methods such as "Electronic" and "Wire" can be found as pre-seeded data. If
required new payment methods can be created and duplicated:
Payment Process
Profiles Payment process profiles are also seeded but can be customized or duplicated
for specific usage:
Disbursement System Options
After defining the setups for funds disbursement, payments manager within the
payables function can be used to define detailed setups based on individual
requirements:
Funds Capturing Setup

Funds capturing setup is used with the focus on inbound payments.
Funds capturing setup steps:
Payment Methods
Payment methods are seeded, but can also be created on request.
Funds Capturing Process
Profiles For a German implementation direct debit payment methods with the type
"Lastschriftverfahren" and "Einzugsermchtigung" are key requirements.
A direct debit funds capturing profile can be found as seeded data for duplication:
Seeded Profiles cannot be used but they can be duplicated and tailored. The important
field to be assigned in the duplicated versions is the transmission configuration.
Payee
The definition of a payee completes the funds capturing setup. Payees have to be
created including:
Payment System and Payment System Account
At least one Operating Unit Assignment
Using multiple Operating Units would assume that they are all part of the same
ledger
Funds Capturing Process Profile
Collections
With Oracle e-Business Suite R12, much of the AR Collections functionality is replaced
by Advanced Collections functionality. Advanced Collections supports a number of
innovative processes and concepts that are different from traditional collections
practices. It's important to understand these concepts and to know how Advanced
Collections uses them. For additional information refer to the Oracle Advanced
Collections Implementation Guide and Oracle Advanced Collections User Guide
available on OracleMetaLink.
Transactions
In Receivables, an invoice, debit memo, credit memo, chargeback, or bill receivable.
Receivables maintains transaction tables which Advanced Collections accesses. Invoices
can include one or more payment schedules.
Delinquency
In Advanced Collections, this is a transaction that is overdue. The criteria used to
determine which transactions are delinquent are configurable. The seeded delinquency
configuration uses a payment schedule for which the dispute amount is less than the
total amount overdue and the due date is prior to the current date to determine
delinquency. Delinquencies are identified from invoices, charge backs and debit
memos. Advanced Collections identifies delinquencies by running a 'delinquency status
determination' concurrent program and maintains this information in delinquency
tables.
Collector's Work Queue
The Universal Work Queue provides a high-level list of all actionable work assigned to,
or owned by, a collections agent. This work is automatically 'pushed' to the agent as
part of the automated collections management flow provided by Oracle Advanced
Collections.
Scoring Engines and Scoring Components
Scoring engines consist of one or more scoring components and they can be configured
to provide a score at the customer, account, and bill to level. Advanced Collections uses
configurable scoring engines for two purposes: to determine whether a transaction is
delinquent and to determine the business value - or collections score - of customers.
Collections scores are similar to a customer's credit score but they generally guide how
seriously the customer is treated during collection activities.
Dunning Plan
The traditional method used to notify a delinquent customer about an unpaid balance.
Advanced Collections provides the ability to send dunning letters via fax, e-mail or
printed letter. Additionally, Collections can use the customer's collections score and the
oldest aged invoice to determine the content and delivery method of the dunning
notice. If payment is not made within a specified period of time, Advanced Collections
can automatically assign a 'dunning callback' to a collector who will then see that action
on their Task node in the Collector Work Queue.
Collections Strategy
Compared to Dunning Plans, this collections method supports more complex means to
contact and manage customers about their receivables situation. Collections strategies
consist of one or more work items, which are actions performed by either the system
(send a reminder letter) or the collector (call this customer). Work items are timed to be
executed serially. Strategies are based on collections scores so different strategies can be
used for customers with 'good' or 'bad' value scores. Collections strategies can also be
used to alert pre-delinquent customers about a pending payment. Unless a deploying
organization has no need to do anything more complex than simple dunning, the best
practice recommendation is to use collections strategies. This allows for flexibility as the
organization changes in the future.
Assets
Setting up Asset Books
Allow Amortized Adjustments
Activate this option using the (Resp) FA Super User (M) Setup/ Asset System/ Book
Controls (Tab) Accounting Rules in order to ease the reconciliation of the depreciation
amount (recalculating the depreciation).
Retirement Accounts
While setting up the accounts for the Retirement transaction in the Asset Book Form, it
should be considered to use different accounts per transaction. There is no need to
setup different accounts for "Gain" and "Loss". For the Retirement it is recommended to
use a different Clearing Account than the Clearing Account used for Mass Additions.
This helps with the reconciliation of the transactions in the GL.
Additional Asset Books

Often an additional Asset Book is being used to reflect country-specific legal
requirements. It is mandatory to link these additional Books to the appropriate Ledgers.
For example, if the Primary Ledger is based on IFRS Accounting Standards, the linked
Asset Book has to reflect IFRS as well.
Optional: Security by book
If there should be a strict separation between the different books for the valuation of
assets, setup this feature to separate the data per Responsibility and per Asset book or
optionally for a number of Asset Books.

Setup at least one responsibility for each book in order to access assets stored in this
book.
EBusiness Tax
Introduction / Remarks
It is common business practice in Germany to enter and post manual journals with taxes
directly in the General Ledger instead of using the subledger modules.
The following setup will not share the tax statuses across Payables and Receivables. Tax
Status has been setup separately for Payables and Receivables. This has been achieved
by setting up specific Tax Rules.
E-Business Tax Setup Regime to Rate flow - Overview

The applications module E-Business Tax is a rule-based engine, which empowers the
user to automatically derive the tax rates based on the transactions and parameters that
have been entered. For a complete setup of the E-Business Tax module please follow the
Regime to Rate flow as shown in the following screen-shot with the 4 levels Regime,
Tax, Status and Rate. In each step there are specific setups necessary.
For Germany taxes should be separated into input and output types:
Tax regimes
Set up tax regimes for the taxes in each country and geographic region where you do
business and where a separate tax applies. A tax regime associates a common set of
default information, regulations, fiscal classifications and registrations to one or more
taxes with the same tax requirement.
The tax regime provides these functions:
Groups similar taxes together.
Designates the geography within which taxes apply.
Defaults the settings and values you define to each tax in the regime.
Contributes to the definition of configuration options and third party service

subscriptions.
Optionally provides a single registration for all taxes associated with the regime.
Defines the use of fiscal classifications.
The common tax regime setup is one tax regime per country per tax type, with the tax
requirements administered by a government tax authority for the entire country.
The main region requires the following information:
Additional the Controls and Defaults are to be defined.
Taxes
Each separate tax in a tax regime includes records for the statuses, rates, and rules that
are used to calculate and report on the tax. E-Business Tax defaults tax information
from the tax regime to each tax that you create under a regime.
You can only enable a tax for use on transactions after you have completed all of the
related setup required. This is achieved by enabling the option: "Make Tax Available for
Transactions" in the last step of your setup.
Additionally the Controls and Defaults are to be defined.
Status
A tax status is the taxable nature of a product in the context of a transaction and a
specific tax on the transaction. Every tax status in Oracle E-Business Tax is defined
under a tax and contains one or more tax rates.
For example, one tax can have separate tax statuses for standard, zero, exemption, and
reduced rates. A zero rate tax status may have multiple zero rates associated with it in
order to handle different reporting requirements for zero rate usage, such as Intra EU,
zero-rated products, or zero-rated exports.
You define a tax status under a tax and a configuration owner, and define all applicable
tax rates and their effective periods under the tax status. The tax status controls the
defaulting of values to its tax rates.
In principal a tax status can be used for Payables and Receivables transactions.
Jurisdictions
A tax jurisdiction is a geographic region or tax zone where a specific tax authority levies
a tax. A tax jurisdiction specifies the association between a tax and a geographic
location.
At transaction time E-Business Tax derives the jurisdiction or jurisdictions that apply to
a transaction line based on the place of supply. The place of supply is the location where a
transaction is determined to take place for a specific tax. E-Business Tax either uses a
default place of supply or derives a place of supply based on tax rules.
You must set up at least one tax jurisdiction for a tax before you can make the tax
available on transactions.
Jurisdiction Setup for Germany:
Tax Rates
Set up tax rates for the tax statuses and tax jurisdictions. For tax statuses, set up a tax
rate record for each applicable tax rate that a tax status identifies. For tax jurisdictions,
set up tax rate records to identify the tax rate variations for a specific tax within
different tax jurisdictions. For example, a city sales tax for a state or province may
contain separate city tax jurisdictions, each with a specific rate for the same tax.
You can also define tax recovery rates to claim full or partial recovery of taxes paid.
You define tax rate codes and rate detail information per rate period. Rate periods
account for changes in tax rates over time. A tax rate code can also identify a
corresponding General Ledger taxable journal entry.
Rate Details
Tax Accounts
Rules
The E-Business Tax determination process uses your tax configuration setup and the
details on the transaction to determine:
Which taxes apply to the transaction.
How to calculate the tax amount for each tax that applies to the transaction.
With E-Business Tax rules there will be a tax determination model created to reflect the
tax regulations of different tax regimes and the tax requirements of your business. To
create a simple tax model that makes use of default values without extensive
processing, or a complex tax model that considers each tax requirement related to a
transaction before making the final calculation.
During execution of the tax determination process, E-Business Tax evaluates, in order of
priority, the tax rules that have defined against the tax configuration setup and the
details on the transaction. If the first rule is successfully evaluated, the result associated
with the rule is used. If not, the next rule is evaluated until either a successful
evaluation or default value is found.
The E-Business Tax determination process is organized into rule types. Each rule type
identifies a particular step in the determination and calculation of taxes on transactions.
The tax line determination process uses the information of the transaction header and
transaction line to determine the tax lines.
The rule types and related processes used for tax line determination and tax calculation
are:
1.
Determine Place of Supply - Determines the location where a transaction is

considered to have taken place for a specific tax.
2.
Determine Tax Applicability - Determines the taxes that apply to a given

transaction.
3.
Determine Tax Registration - Determines the party whose tax registration status is
considered for an applicable tax on the transaction.
4.
Determine Tax Status - Determines the tax status of each applicable tax on the
transaction.
5.
Determine Tax Rate - Determines the tax rate for each applicable tax on the
transaction.
6.
Determine Taxable Basis - Determines the amount upon which to apply the tax
rate.
7.
Calculate Tax Amounts - Calculates the tax amount for each applicable tax on the
transaction.
Example for Determine Tax Status:
Specific Rule Setup for Payable / Receivable Tax Separation

Party Tax Profile
Fiscal Classification Type has to include Sales Transaction and Purchase Transaction
Determine Tax Status in Tax Rules setup to restrict a tax status to be used only in
payables:
Bill To Party has to be set to Purchase Transactions.

Determine Tax Status in Tax Rules setup to restrict a tax status to be used only in
Receivables:
Bill From Party has to be set to Sales Transaction.
3
Process Related Recommendations and
Considerations
Over All
The following section will give some further recommendations on the several business
processes.
Patch Level
It is recommended to use latest available patch levels.
Subledger Accounting Method

There are several predefined Subledger Accounting Methods available. If the Subledger
Accounting Method being used is not a seeded one, it is recommended to document in
detail all objects of the user-defined method.
General Ledger
Manual Journal entries with VAT
Postings on Tax accounts are only shown in the localized VAT reports, if they are
generated by the standard feature for tax within the journal entry form.
Process Related Recommendations and Considerations 3-1
Postings directly to the VAT-Account will not be shown in tax reporting because the tax
code is not referenced. .
Closing Periods within General Ledger
It is possible to close periods in General Ledger while there are still unposted journals.
An organizational process should be put in place, which ensures that all journals are
posted before closing the period. It is not recommended to close a period permanently
until after the auditors have completed the year-end certification.
Freeze Journals
Journal sources can be frozen and unfrozen. It is recommended not to unfreeze a

journal source. Unfrozen journals can be modified or deleted. This could cause major
reconciliation issues.
Payables
Invoice GL-Date Mechanism
Entering the invoice header includes the field GL-Date and represents the liability
accounting. If this GL-Date is changed a warning-message is shown.
The GL-Date on invoice line level represents the expense accounting and is defaulted
from the invoice header level. It is recommended to ensure that GL-Dates on line level
are accurate, because they impact the accounting.
Discount Invoices/Credit Memo fully applied

When invoices are reduced in full by applying a credit memo, it has to be ensured that
payment terms and corresponding discounts are synchronized.
If payment terms are not in line with both documents, the remaining discount can be set
to zero during the payment run.
Discount Partial Payments

When partially paying an invoice the system suggests the full discount amount to be
taken based on the invoice information. A manual correction to the discount is needed,
to ensure correct documentation and accounting for this transaction.
Payable Options, Single Payment, Allow Pre-Date

Oracle standard functionality does not allow creation of a payment with a date that is
earlier than the system date, unless the setup is extended to allow pre-date option in the
payable options form.
If the feature "allow pre-date" is going to be used, additional organizational measures

should be defined to ensure the correctness of the payment date.
It is recommended that periods are closed at the month end to ensure the completeness
of transactions
Supplier duplications
To prevent supplier duplications it is recommended to use naming conventions as well
as internal controls.
Internal control procedures should evaluate, if the supplier to be added exists already in
the system.
Supplier Bank Account Data

To ensure that suppliers bank account assignments are properly documented, it is
recommended to enable auditing. A report has to be created to show the content for this
audit.
Receivables
Customer Duplications
To prevent customer duplications it is recommended to use naming conventions as well
as internal controls.
Internal control procedures should evaluate, if the customer to be added, exists already
in the system
Customer Bank Account Data

To ensure that customer bank account assignments are properly documented, it is
recommended to enable auditing. A report has to be created to show the content for this
audit.
Customer Account Merge

With this function, the user can merge two customers into one remaining customer. All
transactions owned by the original customer will be moved to the "new" customer.
Optionally, the original customer can be deleted after the merge has been run. It is not
recommended to set this option. If the user wants to use this option, it is suggested to
have audit trail function in place including customer master data.
Prepayments (ISTversteuerung von Anzahlungen)

In order to create the correct accounting in AR the following steps are recommended:
Setup: Additional Transaction Type "Prepayment", with interims accounts for

prepayments:
Process (Step1): Enter the cash receipt
Process (Step2): Enter the "prepayment invoice".
Process (Step3): The final invoice will be entered as standard invoice, but with the
manual entry of the "prepayment invoice"(+ tax) as a negative amount.
Accounting of the final invoice must net off the interim accounting of the
"prepayment invoice".
Freight
Freight generation should be done based on Item, to calculate tax on top of the freight
amount.
The standard freight calculation delivered in the AR Workbench by pressing the freight
button should not be used, because it does not create tax on the freight.
Optionally, the freight button can be disabled by unchecking the allow freight option in
the transaction types definition.
Invoice Printing
It is recommended to use the standard invoice printing process.
If using the online button in the invoice workbench it must be ensured by
organizational measures that the data will not be changed anymore.
Alternatively the print button can be excluded from the responsibility:
Receipt Overapplication
If the overapplication feature is used, organizational measures should be in place to
ensure the correct application of the receipts.
Cross Payables/Receivables
AP/AR-Netting
Based on netting agreements, netting batches can be generated for netting of liabilities
and receivables within the trading partners defined in the netting agreement.
Netting agreements can be defined even if the trading partners are not the same legal
entity. Therefore it has to be ensured that netting agreements includes only those
trading partners, which are in line with legislation to net off transactions.
Local legal requirements determine which single transactions can be netted. So, it is
suggested to setup netting batch creation with a manual review step, before finally
approving and generating the netting transactions.
Refunds
Since the introduction of Oracle Payments in R12 the refund feature can be used to pay
credit memos to a customer. This function will create a refund invoice in Payables,
which can be paid by using the payment manager within Payables. In parallel, the
refund is applied to close the credit memo:
Payments
Payments - Overview
With the introduction of Oracle Payments as an integrated platform for inbound and
outbound payments, core processes to create payments has changed accordingly.
The following chapter describes the funds disbursement and the funds capturing
process as an example only.
Funds disbursement
From the Payables responsibility, navigate to "Payments/Entry/Payments Manager".
You can also navigate within the funds disbursement process manager.
Templates
Templates can be setup to be used during the payment process request during the
payment run. Within the template definition a lot of information can be defaulted or left
blank to be entered during the payment process request. Key elements to design a
template are the following:
Payment selection criteria

: Pay Groups, Legal Entities, Organizations, Payment Method, etc.
Payment attributes:
Bank Account, Payment Document, Payment Process Profile, and Exchange Rate
etc.
Process Automation Options
Validation Failure Results
Additional Information
It is recommended to design a template with process automation options, which

enables the user to intervene in the payment process.
Within the template tab the payment request can be started as a single payment request
or a repeating request can be scheduled.
Payment Process Requests

By creating the single payment request the payment process is going to be started.
Preceded values based on the template definition are offered and can be changed.
Mandatory fields have to be completed at this stage.
Based on the process automation options the payment process request can be reviewed,
edited and finally submitted:
The "Payment Dashboard" indicates the actual status of the payment process request:
Scrolling down in the completed payment process request will enable all information:
Click on "Payment Process Request" .
Within the concurrent requests form, the formatting request has been created.
The following output files are created:

Selected Payments Schedules Report
Format Payment Instructions

The output is the bank file:
Payment File Accompanying Letter
Fund Capturing
Creating a direct debit run (Lastschriftlauf/Einzugsermchtigung) would consist from
the following steps:
Create automatic receipt batch (Receivables Manager)
Create remittance batch (Receivables Manager)
Create settlement batch (Funds Capturing Process Manager)
In the last step the following outputs will be delivered:
File for funds capturing (Local File System)
Receipt of Payment Notification (Optional)
Accompanying Letter to authorize the bank
Before running the new step "Create Settlement", it is recommended to check whether
authorized transactions are available in payments. These can be found in the
"Authorizations" tab on the funds capturing process manager home page:
Transactions which are found here, are transmitted by the remittance batch procedure:
The create settlement process can be started from the standard view -> request form or
directly on the Funds Capturing Process Manager Homepage.
Assets
Asset Numbering
If the option to use "automatic numbering" is activated in FA, all assets will have a
gapless number. But, it is possible to enter an alphanumeric number, which will lead to
a "non-gapless" sequence.
Users should take measures to endure that this is not happening
Depreciation calculation according to 7 II Einkommenssteuergesetz (EStG)

In the standard environment, there is no depreciation method defined which follows
the regulations of 7 II EStG.
Formulas or table-based depreciation methods can be used to achieve the regulations of
this requirement.
Unplanned Depreciation and Cost Adjustments

In order to enter unplanned depreciation and cost adjustments, and to calculate the
correct depreciation, activate the feature "Amortize Adjustments".
Then the Assets Net Book value will be recalculated based on the assets remaining life
and the depreciation method.
Adding Costs to an existing Asset

It is possible to show added costs to an existing asset (AHK Erhhung), in the
Addition-Column of the Asset Summary Report if the best practice will used to add an
additional asset. To have a link between both assets the sequence might be changed
(e.g. Asset number 100a for this additional asset). It is important to also check the
remaining life of this asset.
Changing seeded asset details

It is recommended to add Assets only by using the Mass Addition interface with
invoices coming from Accounts Payable.
If assets are added manually, change important asset details such as Useful Life or
Depreciation method. This information is defaulted by the selected Asset Category.
The user should also make sure, that this information is not changed during the process
of adding assets.
Localized "Asset Summary Report (Germany)"

The local requirements of 268 (2) HGB can be achieved with the Asset Summary
Report (Germany), with the following column headings Original Asset, Additions,
Retirements, Changes Of Accounts, Cost Adjustments, Accumulated Depreciation,
Depreciation Expense, NBV Ending Period and NBV Beginning Period.
New Localizations R12

There are several localizations available for Oracle's customers. These should help our
customers to manage their business. These localizations are fully supported and can be
found in Metalink (search for "EMEA Add-On Localizations")
In order to complete the certification successfully, the following localizations were
installed.
VAT Reporting
There are four reports available, which help the user to reconcile their VAT.
CLE: Journal Details Report

This localization is using the accounting sequence number, and supports the
reconciliation process
4
Audit Trail
Define Tables to be Audited

The following tables have to be audited. In the event that you have extended the
standard EBS functionality, these extensions should also be audited if they extend or
modify information that is used to create or derive accounting information.
GL
GL Period (Periodenstatus)
TABLE
COLUMNS
GL_PERIOD_STATUSES
APPLICATION_ID (PK)
CLOSING_STATUS
PERIOD_NAME (PK)
SET_OF_BOOKS_ID (PK)
Accounting Flexfield (Kontoflexfelddetails)

TABLE
COLUMNS
FND_FLEX_VALUES_TL
FLEX_VALUE_ID (PK)
LANGUAGE (PK)
DESCRIPTION
FLEX_VALUE_MEANING
Audit Trail 4-1
Exchange Rates (Wechselkursnderungen)

TABLE
COLUMNS
GL_DAILY_RATES
FROM_CURRENCY (PK)
TO_CURRENCY (PK)
CONVERSION_DATE (PK)
CONVERSION_TYPE (PK)
CONVERSION_RATE
Ledger/Ledger Set Changes (Ledger/Ledgerset nderungen)

TABLE
COLUMNS
GL_LEDGERS
LEDGER_ID (PK)
NAME
SHORT_NAME
DESCRIPTION
LEDGER_CATEGORY_CODE
OBJECT_TYPE_CODE
COMPLETION_STATUS_CODE
CHART_OF_ACCOUNTS_ID
CURRENCY_CODE
PERIOD_SET_NAME
GL_LEDGER_SET_NORM_ASSIGN
LEDGER_ID (PK)
LEDGER_SET_ID (PK)
START_DATE
STATUS_CODE
AP
AP Period (Periodenstatus)
TABLE
COLUMNS
GL_PERIOD_STATUSES
APPLICATION_ID (PK)
CLOSING_STATUS
PERIOD_NAME (PK)
Supplier Header & Site Information (Lieferantenheader und site Informationen)

TABLE
COLUMNS
HZ_PARTIES
PARTY_ID (PK)
PARTY_NAME
PARTY_NUMBER
PARTY_TYPE
PERSON_IDENTIFIER
PERSON_FIRST_NAME
PERSON_LAST_NAME
HZ_PARTY_SITES
PARTY_SITE_ID (PK)
LOCATION_ID
REGION
PARTY_SITE_NUMBER
PARTY_SITE_NAME
PARTY_ID
Supplier Bank Account Data (Bankdaten)

TABLE
COLUMNS
Audit Trail 4-3
IBY_EXT_BANK_ACCOUNTS
EXT_BANK_ACCOUNT_ID (PK)
BANK_ACCOUNT_NAME
BANK_ACCOUNT_NUM
BANK_ACCOUNT_TYPE
BANK_ID
BRANCH_ID
AR
AR Period (Periodenstatus)
TABLE
COLUMNS
GL_PERIOD_STATUSES
APPLICATION_ID (PK)
CLOSING_STATUS
PERIOD_NAME (PK)
AR System Parameters (Debitorenoptionen)

TABLE
COLUMNS
AR_SYSTEM_PARAMETERS_ALL
ORG_ID (PK)
SET_OF_BOOKS_ID
ACCOUNTING_METHOD
RUN_GL_JOURNAL_IMPORT_FLAG
CER_SPLIT_AMOUNT
CER_DSO_DAYS
POSTING_DAYS_PER_CYCLE
INVOICE_DELETION_FLAG
GENERATE_CUSTOMER_NUMBER
Customer Header & Site Information (Kundenheader und site Informationen)
TABLE
COLUMNS
HZ_PARTIES
PARTY_ID (PK)
PARTY_NAME
PARTY_NUMBER
PARTY_TYPE
PERSON_IDENTIFIER
PERSON_FIRST_NAME
PERSON_LAST_NAME
HZ_PARTY_SITES
PARTY_SITE_ID (PK)
LOCATION_ID
REGION
PARTY_SITE_NUMBER
PARTY_SITE_NAME
Customer Bank Account Data (Bankdaten)

TABLE
COLUMNS
IBY_EXT_BANK_ACCOUNTS
EXT_BANK_ACCOUNT_ID (PK)
BANK_ACCOUNT_NAME
BANK_ACCOUNT_NUM
BANK_ACCOUNT_TYPE
BANK_ID
BRANCH_ID
Party Merge
TABLE
COLUMNS
Audit Trail 4-5
HZ_MERGE_PARTIES
BATCH_PARTY_ID (PK)
BATCH_ID
FROM_PARTY_ID
TO_PARTY_ID
MERGE_STATUS
Account Merge
TABLE
COLUMNS
RA_CUSTOMER_MERGE_HEADERS
CUSTOMER_MERGE_HEADER_ID(PK)
CUSTOMER_ID
MERGE_REASON_CODE
MERGE_FAIL_MSG
FA
Asset Book Setup (Afa Buch Setup)
TABLE
COLUMNS
FA_BOOK_CONTROLS
BOOK_TYPE_CODE (PK)
BOOK_CLASS
AMORTIZE_FLAG
INITIAL_DATE
LAST_DEPRN_RUN_DATE
SET_OF_BOOKS_ID
DEPRN_CALENDAR
Asset Categories Setup (Anlagegruppensetup)

TABLE
COLUMNS
FA_CATEGORIES_TL
CATEGORY_ID (PK)
LANGUAGE
DESCRIPTION
Depreciation Methods of an Asset (Abschreibungsmethoden einer Anlage)

TABLE
COLUMNS
FA_METHODS
METHOD_CODE (PK)
METHOD_ID (PK)
NAME
DEPRN_BASIS_RULE
DEPRN_BASIS_FORMULA
DEPRN_BASIS_RULE_ID
Asset Prorate Convention Rules

TABLE
COLUMNS
FA_CONVENTION_TYPES
PRORATE_CONVENTION_CODE (PK)
DESCRIPTION
CREATION_DATE
FA_CONVENTIONS
PRORATE_CONVENTION_CODE (PK)
START_DATE (PK)
PRORATE_DATE
Assets and Asset books

TABLE
COLUMNS
Audit Trail 4-7
FA_BOOKS
BOOK_TYPE_CODE
ASSET_ID,
DATE_EFFECTIVE
LIFE_IN_MONTHS
DEPRN_START_DATE
DEPRN_METHOD_CODE
LIFE_IN_MONTHS
ADJUSTED_COST
ORIGINAL_COST
PRORATE_CONVENTION_CODE
PRORATE_DATE
CAPITALIZE_FLAG
DEPRECIATE_FLAG
LAST_UPDATE_DATE
LAST_UPDATED_BY
DATE_INEFFECTIVE
RETIREMENT_ID
RECOVERABLE_COST
LAST_UPDATE_LOGIN
Assets and Asset Description

TABLE
COLUMNS
FA_ADDITIONS_TL
ASSET_ID
LANGUAGE
DESCRIPTION
LAST_UPDATE_DATE
LAST_UPDATED_BY
CREATED_BY
CREATION_DATE
Assets, Asset numbers, Asset Categories

TABLE
COLUMNS
Audit Trail 4-9
FA_ADDITIONS
ASSET_ID
ASSET_NUMBER
ASSET_KEY_CCID
CURRENT_UNITS
ASSET_TYPE
ASSET_CATEGORY_ID
PARENT_ASSET_ID
SERIAL_NUMBER
MODEL_NUMBER
IN_USE_FLAG
OWNED_LEASED
NEW_USED
ATTRIBUTE_CATEGORY_CODE
CONTEXT
LEASE_ID
INVENTORIAL
LAST_UPDATE_DATE
LAST_UPDATED_BY
CREATED_BY
CREATION_DATE
LAST_UPDATE_LOGIN
Assets Asset Distributions

TABLE
COLUMNS
FA_DISTRIBUTION_HISTORY
DISTRIBUTION_ID
BOOK_TYPE_CODE
ASSET_IDUNITS_ASSIGNED
DATE_EFFECTIVE
CODE_COMBINATION_ID
LOCATION_ID
LAST_UPDATE_DATE
LAST_UPDATED_BY
DATE_INEFFECTIVE
ASSIGNED_TORETIREMENT_ID
TRANSACTION_HEADER_ID_OUT
LAST_UPDATE_LOGIN
Functional Setup
Configure the Profile Options
Profile option 'Sign-On: Audit Level' set to 'FORM'
Profile Option 'Audit Trail: Activate' set to 'YES'
Enable Audit on the Table Owner
GL
AR
IBY
FA
Create an Audit Group
Audit Group Name: "Financials Audit Group"
Add tables above to Audit Group
Audit Trail 4-11
Add columns to be audited for each table

Run concurrent request
For updating the audit tables run the Program "Audit Trail Update Tables" (from
System Administrator responsibility)
Audit Trail Report

In System Administrator Responsibility
Create Concurrent Program "Financial Auditing Report", with executable:

"XDODTEXE" and XML output
Add Concurrent Program to required Request Group (e.g. System Administrator,

General Ledger)
In XML Publisher Administrator:
Create Data Definition with same Code as Concurrent Program Short Name
Upload Data Template: XXFINAUD.xml
Create Template and link it to Data Definition
Upload RTF Template "Financials Audit Report.rtf"
Run concurrent request

For audited data: "Financial Auditing Report" (e.g. System Administrator, General
Ledger responsibility)
5
Reconciliation Process
Cash Management
This chapter describes the procedures for performing period-end processing in Oracle
Cash Management Release 12.
Procedures
The following steps are taken for running the period-end processing for Oracle Cash
Management.
1. Complete Daily Cash Management Activities
Complete bank account transfers for the day, validate them, if necessary, and send
payment instructions to the bank.
2. Load Bank Statements
Detailed information from each bank statement, including bank account information,
deposits received by the bank, and checks cleared needs to be entered into Cash
Management. Bank statements can be either manually entered or loaded electronically
from information received directly from the bank.
For organizations with high transaction volumes, bank statements should be loaded
and reconciled on a daily basis.
Refer to: Entering Bank Statements Manually and Loading Bank Statement Open
Interface.
3. Generate Sweep Transactions
To use target balance or zero balance accounts (ZBA) with the banks, the system can
automatically generate transactions to match banking information once the bank posts
the sweeps. Once the bank statements are imported, run the Sweep Transaction
Generation concurrent program. The program will scan the bank statement for sweep
lines and, based on the cash pool setup in the system, create sweep transactions
between the internal bank accounts, which can be accounted for and subsequently
Reconciliation Process 5-1
reconciled.
4. Create Bank Statement Cash flows
To handle recurring items such as bank fees and interest on the bank statements use the
Bank Statement Cash Flow Creation program to create system transactions (cash flows)
to match banking information.
Once the bank statements are imported, run the Bank Statement Creation concurrent
program. This program will scan the bank statement for specific codes, as defined in the
Bank Statement Cash Flow Mapping, and create cash flows, which can be accounted for
and subsequently reconciled.
5. Reconcile Bank Statements
Once detailed bank statement information has been entered into Cash Management, the
information must be reconciled with the subledger transactions.
Cash Management provides two methods to undertake reconciliation:
a) Automatic
Bank statement details are automatically matched and reconciled with subledger
transactions. This method is ideally suited for bank accounts that have a high volume of
transactions.
(Refer to Reconciling Bank Statements Automatically)
b) Manual
This method requires a manual match of bank statement details with subledger
transactions. This method is ideally suited to reconciling bank accounts that have a
small volume of monthly transactions. The manual reconciliation method can also be
used to reconcile any bank statement details, which could not be reconciled
automatically.
(Refer to Reconciling Bank Statements Manually)
6. Create Miscellaneous Transactions
During the reconciliation process, miscellaneous transactions for bank-originated
entries, such as bank charges and errors can be created. Oracle Payables payments or
Oracle Receivables receipts can also be manually created.
Important: The automatic reconciliation process can be set up to create
miscellaneous transactions automatically.
Note: To create transactions during the reconciliation process, re-run
the 'Create Accounting' routine from Oracle Receivables to ensure all

information is transferred to the General Ledger.
6a. Complete Bank Transfers
Complete the bank account transfer whether it is manual or automatic and record the
validation if required before completing the transfer.
7. Run Bank Statement Detail Report
This report shows statement and transaction information for a specific bank account
statement, including bank statement header information, statement line detail, and
reconciled transaction detail.
This report lists any un-reconciled transactions separately with their current status, and
the statement totals for each type of transaction, including the amount entered,
reconciled, un-reconciled, over-reconciled and under-reconciled, and gives the option to
select only un-reconciled statement lines.
8. Run Transactions Available for Reconciliation Report
This report shows all transactions available for reconciliation for a specific bank
account. It lists detailed transaction information for Available Receipts, Available
Payment and Available Journal Entries for reconciliation. Detailed information includes
the Customer, Supplier or Batch Name, Transaction Date, Payment Method,
Transaction Number, Currency, and Amount.
This report only lists void payments if the Show Void Payments option on the Systems
Parameters window is checked. It does not list reversed receipts due to user error nor
does it list the associated original receipts that were not reconciled. This report groups
transactions by status so that void or reversed transactions are separate from other
transactions.
9. Resolve Un-reconciled Statement Lines
Resolve the un-reconciled statement lines by manually reconciling the statement lines to
the available transactions.
10. Post to General Ledger
Create journal entries for eligible accounting events generated by Bank Account
Transfers and Bank Statement Cash Flows by submitting the "Create Accounting"
concurrent program. The program creates and optionally transfers and posts journal
entries to General Ledger.
If the transfer of Journal Entries to General Ledger is not generated immediately, the
"Transfer Journal Entries to GL" concurrent program has to be submitted. Please make
sure you are satisfied with the draft journal entries before creating final accounting.
In addition to creating final accounting entries, the program can be run in a draft mode,
in which case draft journal entries will be created. Such journals cannot be transferred
or posted to General Ledger.
11. Run the GL Reconciliation Report
Use this report to reconcile the General Ledger cash account to a bank statement
balance.
This report lists a balance and an adjusted balance for the bank statement. It also lists a
separate adjustment amount for un-reconciled receipts, payments, and journal entries,
as well as bank errors.

Warning: To ensure that this report is accurate, first perform these
tasks:
Reconcile all statements in Cash Management.
Transfer journal entry transactions from Oracle Payables and

Oracle Receivables to the General Ledger.
* Post journals in General Ledger, if transfer from sub-ledgers was

not in FINAL POST mode.
12. Run the Account Analysis Report for the General Ledger Cash Account
Run the Account Analysis Report from General Ledger for the General Ledger Cash
Account Flexfield and sort by Source. 13. Review the Account Analysis Report
Review the Account Analysis Report to ensure that only bank account related
transactions have been posted to the General Ledger Cash Account by checking the
Source of the transactions. Valid sources will include Payables and Receivables.
Transactions entered directly via General Ledger will have a Source of Manual or
possibly Spreadsheet if ADI is used.
14. Correct any Invalid Entries to the General Ledger Cash Account
(Optional)
Reverse or amend any journals incorrectly posted to the General Ledger Cash Account,
which were highlighted during the review of the Account Analysis Report.
Payables
Procedures
Payables Release 12.
1. Complete All Transactions for the Period Being Closed
Ensure that all transactions have been entered for the period being closed. Completing
all transactions for Oracle Payables:
Complete Invoices and Credits
Complete Prepayments
Complete Expense Reports
Complete Invoice Import
Complete Payments
To import transactions from an external system using Internet Expenses or Xpense

Xpress, ensure to import all transactions and review all audit trails for completeness.
One consideration for Accounts Payable where there are multiple operating units
within the same ledger is that all operating units must be ready to close at the same
time. All of the operating units that share a ledger also share the same period statuses.
When updating the period status to 'open' in one operating unit, that period is opened
for all operating units within the ledger.
To attempt to update the period status to 'closed' in one operating unit, the system
checks for unposted transactions in all operating units within the ledger. If there are
unposted transactions in any of the operating units, the system asks to resolve the
unposted transactions for those operating units before it allows closing the period for
the ledger. If Multi-org Access Control is implemented, period closing can be performed
across OU's from a single responsibility, through one OU at a time.
2. Run the Payables Approval Process for All Invoices
Run the Payables Approval process to approve all unapproved invoices and invoice
lines in the system, so that they can be paid by Oracle Payments and posted to the
General Ledger.
3. Review and Resolve Amounts to Post to the General Ledger
a) Review the Invoice on Hold Report
This report enables review of any holds currently applied to invoices that would
prevent the payment and/or posting of these invoices. The report details all invoices
that Oracle Payables cannot select for posting and therefore cannot create journal
entries.
Where possible, resolve any identified holds, which will prevent posting to the General
Ledger, and then re-run the Payables Approval process to approve these invoices.
b) Review the Journal Entries Report
This report enables review and analysis of accounting entries in the Payables subledger,
as accounted by SLA. Use the report parameters to produce a detailed or summary
listing of the accounting information to review.
This report is owned by SLA. The report also lists, in detail, transactions that have been
accounted with error and all entries that could not be transferred to the General Ledger.
When a transaction is accounted with errors, review the details and make necessary
changes.
By altering the parameters, the report also lists those transactions, which have been
posted in the General Ledger, and those that have not been posted but have been
accounted.
SLA groups the report by ledger, ledger currency, source, category, and event class.
Data is then sorted by accounting date, event type, supplier name, document number
and voucher number.
c) Review the Unaccounted Transactions Report

This report enables the review of all unaccounted invoice and payment transactions and
a view of the reason that Payables cannot account for a transaction. Accounts Payable
sorts the report by transaction type (invoice or payment), exception, supplier,
transaction currency, and transaction number. Run this report after running the Create
Accounting Process.
The report will then show only transactions that had problems that prevented
accounting. Correct the problems and resubmit the accounting process.
Important: This report does not include invoices that have no
distributions.
d) Optionally run a Payment Process Request at the month end

By running a month end Payment Process request, there will be created a payment for
as many due invoices as possible.
e) Confirm all Payment Instructions
Run the Payment Instruction Register for the period that is to be closed, or finalize any
outstanding payments. Use Oracle Payments to confirm any payment instructions.
Check the status of the Payment Process Request/Payments/Payment Instructions to
ensure that all payments have been processed.
The Payment Instruction Register lists each payment created for a payment process
profile or for a manual payment. Actual payments can be compared against this register
to verify that Oracle Payables/Oracle Payments has recorded payments correctly. The
report lists each payment in a payment process request, including setup and overflow
payment documents, in ascending order, by payment number. This report is
automatically submitted when payment instructions are being created and can also be
submitted from the SRS screen.
Important: Oracle Payables prevents the closing of a period in which all
payments have not been confirmed.
f) Optionally run the Payments Register

The Payment Register details payments printed in a particular accounting period. This
report can be used to review payment activity for each bank account used during the
specified time period.
Warning: The report total only shows the net (less discounts) payment
amount, whereas the Posted Payment Register total is the total

payment amount, including discounts. If only verifying report totals,
these two reports would not balance. Therefore it is necessary to
subtract the 'Discounts Taken' from the Posted Payment Register report
total and then compare this calculated amount to the total displayed on
the Payments Register Report.
4. Reconcile Payments to Bank Statement Activity for the Period

Refer to Chapter 4 Period-End Procedures for Oracle Cash Management.
5. Transfer All Approved Invoices and Payments to the General Ledger
Release 12 provides 3 modes of accounting: Final, Final Post and Draft. The transactions
that have been accounted in Final Post have already been transferred to, and posted in
the General Ledger. The transactions that have been accounted in the Final Mode have
been transferred to GL or can still be within the subledger based on the parameter
Transfer to General Ledger (either 'Yes or 'No') in the Create Accounting program.
When accounting mode is Final and transfer to GL is set to 'No', then the "Transfer
Journal Entries to GL" program needs to be run from the Standard Report Submission
(SRS) window. Please review the "Transfer Journal Entries to GL" report generated by
this program; make sure there are no errors reported on this report.
The transactions in draft accounting mode can be included on accounting reports but
cannot be transferred to the General Ledger. A draft entry does not update balances and
does not reserve funds.
SLA creates detail or summary journal entries for all eligible events during posting. The
journal entries are posted in Oracle General Ledger to update account balances.
Invoice journal entries debit the expense or other account entered on an invoice
distribution line, and credit the liability account specified on the invoice, unless the SLA
rules are not modified to create alternative accounting entries to address the specific
business needs.
Payment journal entries debit the liability account and credit the cash account of the
bank account used to pay an invoice.
The Create Accounting process transfers data to the General Ledger tables, creating
journal entries for these invoice and payment transactions. Posting is determined by the
parameter 'Post in GL' which is set during Create Accounting.
Important: The generated journal batch needs to be posted from within
Oracle General Ledger if the mode of accounting was 'Final', Transfer to

General Ledger was 'Yes' and Post in GL was set to 'No'.
The journal batch will be automatically posted in General Ledger if the mode of
accounting was 'FINAL' and Post in GL was set to 'Yes'.
6. Review the Payables to General Ledger Posting process After Completion.
The following reports can be run to review the invoices and payments that were posted
to Oracle General Ledger, from Oracle Payables, for the period that is to be closed, i.e.
the current accounting period.
a) The Subledger Accounting Program Report generated by the Create Accounting

program.
This report provides either the summary or details (dependent on the parameters
provided during Create Accounting program) of the subledger journal entries created
as a result of running "Create Accounting Program". This report also provides any
errors that may have occurred during generation of the journal entries.
b) The Posted Invoices Register
This report is used to review invoices for which information has been posted to Oracle
General Ledger to create journal entries, and can be used to verify that the total invoice
amount equals the total invoice distribution amount. The report lists each Accounts
Payable Liability Accounting Flexfield and the invoices posted to the account.
c) The Posted Payments Register
This report is used to review the payments posted to Oracle General Ledger during a
particular accounting period, and can be used to review the payment activity for each
bank account used during that period.
7. Close the Current Oracle Payables Period
Close the accounting period by using the Control Payables Periods window to set the
Period Status to 'Closed'. This process automatically submits the Subledger Period
Close Exceptions Report.
The Subledger Period Close Exceptions Report lists all accounting events and journal
entries that fail period close validation. It is automatically submitted by General Ledger
when closing a GL period if there are unprocessed accounting events or un-transferred
journal entries.
Generate the Subledger Period Close Exceptions Report through a concurrent request as
follows:
For the application associated with the responsibility
For all applications in the General Ledger responsibility
8. Reconcile Oracle Payables Activity for the Period

a) Run the Open Account AP Balance Listing Report
This report basically generates the Payables trial balance that can be used for
reconciliation of the total accounts payable liabilities in Oracle Payables, with the Oracle
General Ledger Creditors Control Account for a specific accounting period. The Open
Account AP Balance Listing is based on a Subledger Accounting extract and enables the
identification of the open Accounts Payable transactions that make up each Accounts
Payable balance.
Please refer to the Metalink note # 604739.1 for more details on this report. The report
provides details of the outstanding accounts payable liability for the organization.
To obtain the most up-to-date trial balance for a given period, journal entries should be
posted for the invoice and payment activity for the period, prior to running the report.
For reconciliation of Oracle Payables and Oracle General Ledger when posting is only
performed at period end, the following reconciliation method can be used:
Use the following reports to reconcile transferred invoices and payments to the Open
Account AP Balance Listing Report to ensure that the Trial Balance accurately reflects
the Accounts Payable liability:
Open Account AP Balance Listing Report (for last day of prior period). This is run
to generate the trial balance as of last day of prior period.
Payables Posted Invoice Register - Invoice journals must be posted in General

Ledger to appear on this report.
Payables Posted Payment Register - Payment journals must be posted in General

Ledger to appear on this report.
Open Account AP Balance Listing Report (for last day of current period). This is run
to generate the trial balance as of last day of current period)
This balancing process will help to ensure that all liabilities recorded in Payables are
reflected in the General Ledger AP liability accounts. If the balance reported by the
Open Account AP Balance Listing Report does not equal the balance in the AP liability
account, use the Account Analysis report and the General Ledger reports to determine
which journals are being posted to that account. Before running the reports, run the
Transfer Journal Entries to GL Program for all transactions in the period that will be
reconciled. Also, be sure to post the transactions in the General Ledger.
Important: Typical AP/GL Reconciliation Example
31st March Open Account AP Balance Listing Report

+ April Payables Posted Invoice Register
April Payables Posted Payment Register
- 30th April Open Account AP Balance Listing Report= 0
b) Submit and review Account Analysis Report

The Account Analysis Report provides drill-down information about the movement on
a particular account for a period or range of periods. It only includes journal entries
transferred to and posted to General Ledger.
Review this report and compare it with the 'Third Party Balances' report. This report is
owned by SLA.
Important: avoid duplication with subledger journal entries, General
Ledger journal entries imported from SLA are not included in the
report.
9. Run Mass Additions Transfer to Oracle Assets

Complete all Payables transaction entries and confirm all invoice holds, and carry
forwards, submit the Mass Additions Create program to transfer capital invoice line
distributions from Oracle Payables to Oracle Assets.
For foreign currency assets, Payables sends the invoice distribution amount in the
converted functional currency. The mass addition line appears in Oracle Assets with the
functional currency amount.
Create mass additions and review them in the Prepare Mass Additions window in
Oracle Assets.
It is recommended to do a final Mass Additions Create after the period close to ensure
that all Payables invoices are:
Included in the correct period and
Any additional invoicing will become part of the next periods invoice and asset
processing period.
Tip: If the volume of transactions in Accounts Payable requiring Assets
update is large, it is recommended to run the Mass Additions Create

process on a more regular basis.
10. Open the Next Oracle Payables Period

Open the next accounting period by using the Control Payables Periods window to set
the period status to Open.
11. Run Reports for Tax Reporting Purposes (Optional)
A variety of standard reports can be used to provide tax information, which is required
to be reported to the relevant Tax Authority: The following tax reports are available:
CLE: German VAT Detailed Transaction Report
CLE: Germany VAT Detailed Reconciliation Report
CLE: Germany VAT Preliminary VAT Declaration Report
CLE: VAT Transactions with Differences Report
Receivables
Receivables Release 12.
Procedures
The following steps are taken in performing period-end processing for Oracle
Receivables.
Ensure that all transactions have been entered for the period being closed.
To import transactions from an external system or Oracle Projects, ensure that all
transactions and master files have been imported, and review all audit trails for
completeness.
2. Reconcile Transaction Activity for the Period
Reconcile the transaction activity in Oracle Receivables, before posting to the General
Ledger using SLA. This reconciliation process checks that Oracle Receivables
transactions are balanced, ensuring that all items eligible for posting are reflected on the
Sales Journal. Run the following reports for the same accounting period date range:
a. Transaction Register
This report lists all the transactions (i.e. invoices, debit memos, credit memos, deposits,
guarantees and charge backs) entered with a GL date between the period start and
period end dates specified for the period being reconciled. This report shows
transactions, which were entered and completed.
b. Sales Journal by Customer Report and the Sales Journal by GL Account Report
This report enables the review of all transactions for the specified period. The summary
totals for the sales journal are by Posting Status, Company, and Transaction Currency.
This report details, by account type (i.e. receivables, revenue, freight, tax), the General
Ledger distributions for posted and/or un-posted invoices for the specified period.
The total on the Sales Journal by GL Account should equal the total of items eligible for
posting as listed on the Transaction Register. If any discrepancies are evident, research
the customer balances to find out which balance does not tally, using the Sales Journal
by Customer report.
By using the following formula, ensure that the Transaction Register matches the Sales
Journal:
Transaction Register (Items eligible for posting + 2 * Credit Memo Total = Sales Journal
(Debits plus Credits)
Example
$100 + (2 * $20) = Debits $120 + Credits $20
($120 Debits - $20 Credits)
Important: The Transaction Register total for any credits must be
adjusted, as they are negative on the Transaction Register and positive

on the Sales Journal.
Important: Ensure that the monthly transaction total is accurate and
that no accounting distribution line issues exist.
c. Journal Entries Report

This report enables the review and analysis of accounting entries in the Receivables
subledger, as accounted by SLA. Use the report parameters to produce a detailed or
summary listing of the accounting information for the review. This report is owned by
SLA.
The report also lists transactions that have been accounted with error, and all entries
that could not be transferred to the General Ledger in detail. When a transaction is
accounted with errors, review the details and make the necessary changes.
By altering the parameters, the report also lists those transactions, which have been
posted in General Ledger, and those that are yet to be posted but have been accounted.
SLA groups the report by ledger, ledger currency, source, category, and event class.
Data is then sorted by accounting date, event type, supplier name, document number,
and voucher number.
Important: To avoid duplication of subledger journal entries, General
Ledger journal entries imported from Subledger Accounting are not

included in the report.
d. AR to GL Reconciliation Report
The AR to GL Reconciliation report compares the account balances in Oracle
Receivables to those in Oracle General Ledger, and highlights journal sources where
discrepancies might exist. This report simplifies the reconciliation process by comparing
Receivables and General Ledger account balances in a single place.
Run the AR to GL Reconciliation report:
After the Create Accounting program in Receivables has completed
Review the Unposted Items report to confirm that all journal entries have posted
Use the posting execution reports to confirm that the Journal Entries exported from
Receivables match those posted in General Ledger.
This report will show a difference between Receivables and GL account balances only if
items did not successfully post to GL accounts. The Difference column indicates how
the activity in Receivables compares to the journal source of Receivables in the General
Ledger. If the actual balance of a specific account is different in Receivables than in GL,
then the following columns highlight the type of journals that affect the account
balances:
GL Source Manual - Manual journal entries made in the General Ledger.
GL Subledgers Not AR - Journal entries posted to the General Ledger from other
subledgers, such as Oracle Payables or a legacy feeder system.
Unposted in GL - Unposted journals in the General Ledger.
During the internal reconciliation process, use the AR Reconciliation report to confirm
that the transactional and accounting data match. However, even if the data matches,
the journals could still post to incorrect GL accounts. The Potential Reconciling Items
report addresses this issue by suggesting journal items that might potentially post to GL
accounts with unexpected account types, thus creating reconciliation issues in Oracle
General Ledger.
Important: Where there are multiple operating units within the same
ledger all operating units must be ready to close at the same time. All of
the operating units that share a ledger also share the same period
status. When the period status is updated to 'Open' in one operating
unit, that period is opened for all operating units within the ledger.
3. Reconcile Outstanding Customer Balances

Reconcile the outstanding customer balances at the beginning of a specified period with
the ending balance for the same period, using the following formula, known as the Roll
Forward Formula:
Period End Balance
=
Outstanding Balance at Start of the Period
Transactions
Adjustments
Invoice Exceptions
Applied Receipts
Unapplied Receipts
The following list represents the various components that affect a customer's balance
and the reports, which can be run and reviewed to reconcile these components:
Component
Report
Beginning Balance
Aging reports
Transactions
Transaction Register
Adjustments
Adjustment Register
Exceptions
Invoice Exceptions Report
Applied Receipts
Applied Receipts Register (Identify payments

received from customers)
Unapplied Receipts
Unapplied and Unresolved Receipts Register

(identify payments received from customers)
Unapplied Receipts
Aging report (as of the last day of the

accounting period)
Important: Use the Invoice Exceptions Report to adjust the Transaction
Register for any transactions, which are not open in Receivables, and
therefore do not show up in the aging reports
4. Review the Unapplied and Unresolved Receipts Register

Use the Unapplied and Unresolved Receipts Register to review detailed information
about the customers' on-account and unapplied payments for the date range that is
specified. Use this report to determine how much the customer owes after taking into
account all on-account and unapplied amounts. Receivables displays information about
the on-account or unapplied payment such as GL date, batch source, batch name,
payment method, payment number, payment date, on-account amount, and unapplied
amount. This report includes both cash and miscellaneous receipts.
If any of the Receipts listed can now be applied to outstanding transactions, perform
this action by re-querying the receipts and following the normal application procedure.
5. Reconcile Receipts
Ensure that Oracle Receivables receipts balance by running the following reports:
a) Receipts Journal Report
This report displays details of receipts that appear in the Journal Entries Report. The
Journal Entries Report shows the receipt numbers that contribute to a particular GL
account. Review the detailed information using the receipt number on the Receipts
Journal Report.
b) Receipt Register
Use this report to review a list of receipts for a specified date range.
Important: Normally the total of the Receipts Journal report should
equal the total of all the receipts in the Receipt Register for the same GL
date range
Both reports display invoice related receipts and miscellaneous receipts.

6. Reconcile Receipts to Bank Statement Activity for the Period
(Refer to Chapter 4 Period-End Procedures for Oracle Cash Management)
Important: The Create Accounting process must be re-run for any
miscellaneous accounting entries generated from the bank

reconciliation, for transfer to the General Ledger. This program is
owned by SLA and can be run both from the transactions screen and
also from the SRS screen.
7. Post to the General Ledger

Prior to posting to the General Ledger, the Receipts Journal Report and Sales Journal
Report display the transactions that would be posted to the General Ledger (provided
the posting process was run for the same GL date range). After internally reconciling
the transactions and receipts using these two reports, it is possible to perform external
reconciliation during and after the posting process.
The posting process for Oracle Receivables involves a single step:
Create Accounting
This request, owned by SLA, can be submitted from the transactions screen or even
from the SRS screen. The accounting is done at the ledger level and the program has the
ability to transfer and import into the General Ledger based on the parameters
specified.
If Create Accounting is submitted in the 'Final' mode without transferring it to the
General Ledger, the entries will have to be transferred separately.
8. Reconcile the General Ledger Transfer Process
The Create Accounting program produces the Subledger Accounting Program report
that shows the subledger journal entries created for successful accounting events.
Compare this report to the Journal Entries Report (run in Posted status mode) and
verify that they match. Use the same General Ledger date ranges for the Journal Entries
Report and the Create Accounting program.
Create Accounting will generate a report which details the transferred transactions,
transactions in error etc.
Once transactions and receipts have been transferred to the GL tables, Oracle
Receivables regards these items as having been 'posted' within the sub-ledger. Account
balances for transactions and receipts can be reconciled by generating the Sales Journal
by GL Account Report, the Receipts Journal Report (in 'transaction' mode) and the
Journal Entries Report for posted items. The account totals in the Sales and Receipt
journals should match the corresponding account balances in the Journal Entries
Report.
Important: The 'Detail by Account' version of the Journal Entries Report
may be the most useful for reconciliation in this case.
When running any Oracle Receivables reports that display accounting involving
transactions that have been posted to GL, the following statements apply:
If SLA final accounting lines exist, then SLA accounting is displayed. If SLA accounting
lines do not exist, then AR distribution accounting is displayed.
9. Reconcile the Journal Import Process
The Create Accounting program submits Journal Import automatically when launched
in 'Mode = Final' and 'Transfer to GL = Yes'. Reconcile the Journal Import by manually
reviewing the transactions in the Subledger Accounting Program Report, and
comparing them with the Journal Entries Report output.
The Journal Entries Report is a new Subledger Accounting BI Publisher report which is
available from the subledger applications and can be run with parameter Posted = Yes,
No or ALL, which users can copy and modify the report template according to their
needs.
Important: If the customer is using Reporting/Accounting sequences,
they can run the Journal Entries Report using Sequence Ranges created
by the Create Accounting program, and compare the sum total with the
Journal Import Execution Report. 10. Close the Current Oracle
Receivables Period Close the current period in Oracle Receivables using
the Open/Close Accounting Periods window.
10. Close the Current Oracle Receivables Period

Close the current period in Oracle Receivables using the Open/Close Accounting
Periods window.
11. Review the Subledger Period Close Exceptions Report:
The Subledger Period Close Exceptions Report lists all the accounting events and
journal entries that fail period close validation. It is automatically submitted by General
Ledger when closing a GL period if there are unprocessed accounting events or
un-transferred journal entries.
Generate the Subledger Period Close Exceptions Report through a concurrent request as
follows:
For the application associated with the responsibility
For all applications in the General Ledger responsibility
12. Reconcile Posted Journal Entries

After running the GL posting process in Oracle General Ledger for the transactions that
were transferred in FINAL mode and with Post in GL being set to NO, run the Journal
Entries Report (with 'Posted = Y') to help reconcile the posted journals.
13. Review the Unposted Items Report
Oracle Receivables prints the Unposted Items Report for all items that are not posted for
the specified GL date range. Run the request from the Submit Requests window. The
output will consist of all items not posted to the General Ledger for the specified GL
date range.
Using the Submit Requests window to generate this report, submit with a GL date
range for at least the current financial year. This report should not generate any output
if all Receivables transactions have been successfully posted to the General Ledger.
If there are any items not posted for the current or prior periods, then re-open both
appropriate Receivables and General Ledger Periods and initiate another posting.
14. Review Account Analysis Report
The Account Analysis Report provides drill-down information about the activities
relating to a particular account for a period or range of periods.
It only includes journal entries transferred , and posted to the General Ledger. Review
this report and compare it with the Third Party balances report.
This report is owned by SLA.
Important: To avoid duplication with subledger journal entries,
General Ledger journal entries imported from Subledger Accounting

are not included in the report.
15. Open the Next Oracle Receivables Period

Open the next period in the Oracle Receivables using the Open/Close Accounting
Periods window.
to be reported to the relevant Tax Authority, including withholding tax.
The following tax reports are available:
Assets
Assets Release 12.
Procedures
The following steps are taken in performing period-end processing for Oracle Assets.
Ensure that all transactions have been entered for the period being closed.
Once a depreciation period in Oracle Assets has been closed, it cannot be re-opened.
Check that transactions are not being entered, as Oracle Assets prevents transaction
data entry while the Depreciation Run Process is running.
Completing all transactions for Oracle Assets:
Prepare and Post Mass Additions
Complete Manual Additions
Complete Adjustments
Complete Retirements
Complete Transfers
Complete Reinstatements
2. Assign All Assets to Distribution Lines

If an asset has not been assigned to a distribution line, the period end Depreciation
Process will not complete, and will not close the period. Determine which assets have
not been assigned to a distribution line by running the following report:
Assets Not Assigned to Any Cost Centers Listing
3. Run Calculate Gains and Losses (Optional)

The Calculate Gains and Losses program for retirements can be submitted prior to
running depreciation. The Calculate Gains and Losses process is performed
independently for each depreciation book. The book and depreciation period are
nominated on the Submit Request window.
For books with a large volume of assets, the retirements process can be run several
times during the period to reduce the time for the depreciation process.
Alternatively, the Calculate Gains and Losses program will be submitted as part of the
Run Depreciation Process.

4. Run Depreciation
By running Depreciation, Oracle Assets gives the option of closing the current period if
the Close Period check box on the 'Run Depreciation' window is checked. If all of the
assets depreciate successfully, Oracle Assets automatically closes the period and opens
the next period for the asset book. Oracle Assets does not close the period if the Close
Period check box isn't checked.
Important: Depreciation will be rolled back automatically if any
activity is performed on a depreciated transaction. This is valid only if

the period is not closed.
Tip: Ensure that all transactions have been entered for the period
before depreciation is run. Once the program closes the period, there is
no possibility to reopen.
The Run Depreciation process is performed independently for each asset book. The
asset book and depreciation period are selected on the Run Depreciation window.
When the process is run, Oracle Assets automatically calculates depreciation for all
assets, calculates gains and losses for all retirements, and then runs the appropriate
Reserve Ledger Report.
If an asset has not been assigned to a distribution line, the Run Depreciation process
will end with an error status. By using the depreciation log file the unassigned assets
will be shown, or review the Depreciation Program Report via the Requests window.
The unassigned assets can then be assigned to distribution lines and the Depreciation
process resubmitted. The Depreciation process only processes assets that have not
already been processed.
The Run Depreciation process will close the current depreciation period and open the
next only if the Close Period checkbox is selected.
This process submits concurrent requests to run the calculate gains and losses,
depreciation, and reporting programs off-line.
When the depreciation program is run for an Asset Corporate Book, the Journal Entry
Reserve Ledger Report will be generated. However, if the depreciation program is run
for a Tax book, then the Tax Reserve Ledger Report is generated. Both Reserve Ledger
Reports can also be run at any time, using the Submit Requests window.
5. Create Accounting
Submit the Create Accounting process from SRS screen. This process generates
accounting and also enables transfer to and posting in GL. This program is owned by
SLA. The program can be run in 3 modes: Draft, Final and Final Post. This program
replaces the 'Create Journal Entries' in Oracle Assets. If the program is run in FINAL
mode with POST as yes, then the entries will be automatically posted to the General
Ledger. If the program is run in FINAL mode with 'Transfer to General Ledger' as NO,
then run Transfer Journal Entries to GL Assets later on. For more details, please refer
to the Oracle Assets User Guide.
The depreciation expense journal entries can be created from an Asset Corporate or an
Asset Tax book and transferred to the General Ledger.
There is no need to run depreciation before creating accounting transactions. Run the
Create Accounting process as many times as necessary within a period.
This program creates adjusting journal entries to depreciation expense, bonus expense,
accumulated depreciation accounts, and bonus reserve accounts when entering prior
period additions, transfers, or retirements.
Warning: Journal entries cannot be created from asset budgeting books.
Journal entries can be created for any period in the current fiscal year for which journal
entries have not already been created. The GL period for which journal entries are to be
created must be open.

Oracle Assets uses the 'FA: Use Workflow Account Generation' to make a decision on
whether to use the workflow or not. By default, on upgrade this profile option is set to
'Yes'. If the profile is set to 'No', create accounting will generate accounting based on its
rules and the workflow will not be used.
Important: If in Release 11i the FA Account Generator Workflow was
customized, the customizations will have to be re-implemented using

SLA, or FA: Use Workflow Account Generation should be set as YES. In
the second case workflow will be used to generate accounts.
Important: 'Create Journal Entries' program has now been replaced by
the 'Create Accounting' program.
6. Rollback Depreciation
There is no separate program as in Release 11i to perform the rollback. Any alteration
on a depreciated asset will result in an automatic rollback.
Important: Rollback happens at Asset Level in Release 12, unlike at
Asset Book level as in Release 11i.
7. Depreciation Projections (Optional)

You can project depreciation expense for any number of future periods, on as many as
five depreciation books at once. Results can be summarized by year, quarter, month, or
any specified interval. The results can also be summarized by cost centre or
depreciation expense account.
8. Review and Post Journal Entries

If accounting was performed without the journal entries being posted, review the
unposted journal entries in the Enter Journals window, in Oracle General Ledger. Post
each journal entry batch using the Post Journals window in Oracle General Ledger to
update the account balances.
Optionally, use the More Actions button to post each journal individually or, if the
source of Assets has been included in the Auto Post options, the Assets Journals will be
posted automatically in the next scheduled posting run.
9. Reconcile Oracle Assets to the General Ledger Using Reports
Reserve Ledger Reports
a) Journal Entry Reserve Ledger
Reconcile with the Account Analysis with Payables Details Report.
b) Tax Reserve Ledger Report
Additionally, the Account Reconciliation Reserve Ledger Report can be run.
Balances Reports
a) Cost Detail and Cost Summary Reports
b) CIP Detail and CIP Summary Reports
c) Reserve Detail and Reserve Summary Reports
d) Revaluation Reserve Detail and Revaluation Reserve Summary Reports
e) Account Analysis Report
Transaction Reports
a) Asset Additions Report
b) Cost Adjustments Report
c) Asset Reclassification Report
d) Asset Transfers Report
e) Asset Retirements Report
f) Reinstated Assets Report
g) Cost Clearing Reconciliation Report
General Ledger Reports
a) Unposted Journals Report
Run the General Journals Report for Posting Status = Unposted to reconcile with the
Drill Down reports.
b) Posted Journals Report
Run the General Journals Report for Posting Status = Posted.
c) Account Analysis Report with Payables Detail
The ending balance of this report reconciles with the Reserve Summary Report ending
balance.
d) Financial Statements Generator

It is recommended to create a detailed Financial Statement Generator (FSG) for all asset
accounts. This can be done at cost centre level for direct comparison with the Asset Cost
Summary and Reserve Summary reports.
10. Run Responsibility Reports (Optional)
It is also important to ensure that the asset inventory is accurate. If the asset inventory is
inaccurate, then the financial statements will also be inaccurate.
The following reports can be reviewed when assessing the accuracy of the asset
inventory:
Asset Additions By Cost Centre Report
Asset Additions Responsibility Report
Asset Disposals Responsibility Report
Asset Inventory Report
Asset Retirements by Cost Centre Report
Responsibility Reserve Ledger Report
Asset Summary Report (Germany)
General Ledger
General Ledger Release 12.
Important: The Period-End and Year-End processes are the same if
Encumbrances are Not Used. Special steps are required for

Encumbrances.
Procedures
The following steps are taken in performing period-end processing for Oracle General
Ledger.
1. Ensure the Next Accounting Period Status is set to Future Entry
Set the status of the next accounting period to 'Future Entry' if it is not already done,
except at year-end. (Future entry will enable automatic journals such as reversals to be
generated even if the period is not fully opened)
At year-end, it is recommended to complete all period-end processing, prior to opening
the first period of the new fiscal year.
Maintain period-end exchange rates for all foreign currencies, which should be
translated.
2. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger
Journals are created to enter accounting information into Oracle General Ledger.
Journals are comprised of batch level, journal entry level, and journal entry line level,
information.
Ensure that the accounting information from the sub-ledgers (Oracle Payables,
Purchasing, Inventory, Order Management, Receivables, Cash Management, Assets,
Treasury and Projects) have been transferred to Oracle General Ledger. Run the Create
Accounting program or the appropriate program (based on previous runs of Create
Accounting) to transfer data from the subledgers into Oracle General Ledger. The
Create Accounting process of SLA submits the Journal Import Process (based on
appropriate parameters as discussed in previous sections). This process populates the
GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES tables, and is run
automatically.
Important: The journal posting process, run in Oracle General Ledger,
updates the GL_BALANCES table.
Journal Import:
If not automatically completed, review the Journal Import Execution Report to

identify which journal entry batches were not successfully imported.
Delete any error journal entry batches. Determine the source(s) for these error
batches, and retrieve the run ID from the Journal Import Execution Report.
Re-import these corrected journal entry batches from the GL_INTERFACE table.
Simply re-enter the source from which journal entry batches are to be imported.
Important: If journal import fails when importing from the sub-ledger
modules, data will be rolled back to SLA tables, so that there would not
be any data left in the GL_INTERFACE table, when the profile option
'SLA: Disable Journal Import' is set to 'No'.
Important: Leave sufficient time to re-import any journal entries not
successfully imported from the feeder systems. Then update and post
them.
3. Upload Journals from ADI (Applications Desktop Integrator) to Oracle General

Ledger (Optional)
Journal information can also be imported from spreadsheets into Oracle General Ledger
using Web-ADI (web based Application Desktop Integrator).
4. Complete Non-Oracle Sub-ledger Interfaces to Oracle General Ledger (Optional)

Following the same procedures as for Step 2. Ensure that the accounting information
from any site specific, non-Oracle sub-ledgers has been transferred to Oracle General
Ledger. Run the Journal Import process for these sources and ensure the resulting
Journal Entries are posted either automatically by AutoPost or manually.
Important: It is advisable to use XLA (SLA) interface tables to load
transactions from 3rd party systems rather than using GL_INTERFACE
5. Generate Reversal Journals (Optional)

Select all the journals to be reversed. Submit the process to generate the Reversal
Journals. This process can be run across ledgers.
6. Generate Recurring Journals (Optional)
Select all the Recurring Journals that require generation for the current period. Submit
the process to generate the Recurring Journals. This process can be submitted for
foreign currency and for multiple ledgers, provided the access is available.
7. Generate Mass Allocation Journals (Optional)
Select the Mass Allocation Journals that require generation for the current period.
Ensure that all entries to the source accounting flexfields used in the MassAllocation
Journal definitions are finalized for the current period, prior to generating the journal.
Post the step-down allocations in the correct order (i.e. perform the calculation and
post, for each successive level of allocation entry). This process can be run across
ledgers and across currencies.
8. Review and Verify Journal Details of Unposted Journal Entries
Review any remaining unposted journal entries for the current period. Update journal
entries as appropriate.
Important: Journal entries can be reviewed on-line, or via reports.
Reviewing journal entries prior to posting minimizes the number of

corrections and changes after posting. Following review of journal
entry batches, perform any journal entry updates, including any
adjusting entries, before posting.
Standard Journal reports available include:
Journal Batch Summary Report
Journals - General Report
Journals - Entry Report
Journals - Line Report
Tax Journals Report
General Ledger - Entered Currency
Journals by Document Number Report (when document sequencing is used)
9. Post All Journal Batches

Post all journal entries for the current period, including reversal, recurring and
allocation journals.
Review the results of the post:
The Posting Execution Report facilitates review of the results of journal entry
posting. Oracle General Ledger generates this report every time posting of journal
entry batches occurs. This report indicates any errors in journal entries or journal
entry lines that were discovered during the posting process.
Run the Journals - General Report with a Posting Status of Error Journals to review
error journal entry batches and their journal entries.
Update unpostable journal entries.

Locate the problems with unpostable journal entry batches using the following
information:
a) Control Total
When using a control total, ensure that the debits and credits equal the control total.
b) Period Status
Post Actual batches to open periods.
c) Batch Status
Oracle General Ledger describes the problems with unpostable batches.
Common reasons for unpostable batches are:
Control total violations
Posting to unopened periods
Unbalanced journal entries

Important: All errors in the journal entry batches must be fixed, and the
corrected journal entries re-submitted for posting.
Post updated journal entries.
9a. Run the Period Close Exceptions Report

This is a new step in Release 12. The General Ledger accountant can run the Period
Close Exceptions report to double check that there are no outstanding transactions in
the subledgers and GL, and ensure a follow-up with relevant colleagues if any
exceptions are identified.
10. Run GL Trial Balances and Preliminary Financial Statement Generator Reports
(FSGs)
To maintain a consistent audit trail, it is advisable to create a standard period-end
accounting report set that can be run at each period-end.
Custom accounting reports can be created by using the 'Financial Statement Generator
(FSG)'.
Request financial reports such as:
a) Balance Sheets
b) Income Statements (P&L)
11. Revalue Balances (Optional)
Revalue account balances to update functional currency equivalents.
12. Translate Balances (Optional)
Define any new currencies to which accounting balances are to be translated.
Maintain period-end exchange rates for all foreign currencies, which should be
translated.
Maintain average exchange rates for all foreign currencies, which should be translated.
Maintain historical rates or amounts for any owner's equity accounts to be translated.
Translate account balances to any defined currency.
13. Consolidate Ledgers (Optional)
a) Consolidate Within Ledgers
Enter consolidating journal entries.
The following two methods can be used to create eliminating entries for multiple
companies using a single Ledger:
Automatic Eliminating Entries - define mapping rules to eliminated intercompany

receivables, payables, investments in subsidiaries, intercompany sales etc.
Recurring Journals - use formulas
Post consolidating journal entries.

Define a reporting hierarchy that consolidates all the companies.
Define financial statements with the reporting hierarchy.
b) Consolidate Across Ledgers using the Global Consolidation System (GCS)

Define consolidations and perform revaluation and translation of foreign subsidiaries as
required. Run the consolidations and enter consolidated and eliminating entries. Finally
report on this consolidated ledger using FSG's.
Analyze the results using drill-down capability from Parent ledger to Subsidiary.
14. Review and Correct Balances (Perform Reconciliations)
Oracle General Ledger should be reconciled with all other modules. Adjust journals to
correct any errors in the journals. Create and post adjusting journals to correct errors in
account balances.
Review Detail Account Balances On-line
Review Account Balances via Reports
Request accounting reports such as general ledgers, general journals, trial balances, and
account analysis reports to facilitate reconciliation of Oracle General Ledger with the
other Financials and Manufacturing modules.
a) General Ledger Reports General Ledger Reports facilitate tracing back each
transaction to the original source. These reports list beginning and ending account
balances and all journal entry lines affecting each account balance. The report provides
detailed information on each journal entry line including source, category and date.
b) Accounts Analysis Reports
These reports list the accumulated balances of a range of Accounting Flexfield and all
journal entries that affect that range. Detailed information is provided for each journal
entry line, which includes the source, batch name, and description.
c) Trial Balance Reports
Use trial balance reports to review account balances and activity in summary or detail.
d) Journal Reports
These reports print journal entry batches and include journal entry subtotals,
descriptions and reference information for each journal entry line. Report on foreign
currency, posted, unposted or error journal entries, and report on a specific batch or on
journal entries from a specific source.
Journal Reconciliation:
Transactions in GL can be reconciled by the General Ledger Entry Reconciliation by

accounts that should balance to zero. With General Ledger Entry Reconciliation, the
selectively cross-reference transactions in GL with each other by entering reconciliation
reference information at the journal line level. When the balance for a group of
transactions is zero mark the transactions as reconciled.
Determine the adjusting entries required to net these accounts to zero.
Important: If suspense accounting is not allowed, Oracle General
Ledger will not post out-of-balance batches.
15. Enter Adjustments and / or Accruals and Post

To correct errors in account balances made by posting incorrect journals, create and
post adjusting and reversing journals.
Important: The details of posted journals cannot be changed, except to
mark or unmark for reversal. An incorrectly entered posted journal

must be reversed to back-out the accounting of the original posted
journal.
Other journal entry adjustments, for example, write-offs (refer to Accrual Write-Off
Report), and manual accruals can also be entered into Oracle General Ledger at this
point.
16. Perform Final Adjustments
Enter and Post any final adjustments as required by the organization.
17. Close the Current Oracle General Ledger Period
Close the current GL accounting period in the Open and Close Periods window. The
period can be 'soft closed', if later adjustments to the balances for that period may be
applicable, or 'permanently closed', which means that the period cannot be re-opened in
the future.
This step will need to be repeated for each ledger unless a data access set is setup to
give access to multiple ledgers. This is controlled by GL: Data Access Set profile option.
With a data access set across ledgers programs can be run for multiple ledgers from a
single responsibility. For more information please refer to the Oracle General Ledger
User Guide.
18. Open the Next Oracle General Ledger Period
Open the next General Ledger accounting period in the Open and Close Periods
window. This operation can be performed across ledgers provided the 'Data Access Set'
grants access.
Choose status 'Open' to open a new accounting period, or to re-open a previously soft
closed period to enable adjustments to be made.
Generate and post reversal journals that were entered in the prior period. For example
any Oracle Purchasing receipt accruals and manual accruals.
This step will need to be repeated for each ledger unless a data access set is setup to
give access to multiple ledgers. Any Journals entered into this period while it had a
status of Future Enterable, can now be posted as the period now has a status of Open.
This is controlled by GL: Data Access Set profile option. With a data access set across
ledgers programs can be run for multiple ledgers from a single responsibility.
19. Run Financial Reports for the Closed Period

Run a final Trial Balance Report.
Run final Financial Statement Generator Reports (FSG) or Report Sets as required by the
organization including Income Statements and Balance Sheets. FSGs can also be
published via the Application Desktop Integrator (ADI).
to be reported to the relevant Tax Authority, including withholding tax.
The following tax reports are available:
21. Verify Carry Forward (Optional)

Oracle Financials provides an automatic carry forward of all accounts which are
identified as Balance Sheet accounts
Balance Sheet accounts are identified using the Account Type in the segment value
definition form.
Asset
Liabilities
Ownership / Stockholder's Equity
All other Account Types won't be carried forward

Important: Make sure that the Chart of Accounts has been defined
correctly. Accounts with Account Type Expense and Revenue won't be

carried forward.
6
Reconciliation Reports
Cash Management
Bank Statement Detail Report
Parameters:
Parameters:
Reconciliation Reports 6-1
Output:
Transactions Available for Reconciliation Report

Parameters:
Output:
General Ledger Reconciliation Report

Parameters:
Output:
Account Analysis Report

Parameters:
Output:
Payables
Invoices on Hold Report
Parameters:
Output:
Journal Entries Report

Parameters:
Output:
Unaccounted Transactions Report

Parameters:
Output:
Payment Register
Parameters:
Output:
Subledger Accounting Program Report

The Create Accounting program generates this report
Parameters:
Output:
Posted Invoices Register

Parameters:
Output:
Open Account AP Balance Listing Report

Parameters:
Output:

Parameters:
Output:
Receivables
Transaction Register
Parameters:
Output:
Sales Journal by Customer

Parameters:
Output:
Sales Journal by GL Account Report

Parameters:
Output:
Journal Entry Report

Parameters:
Output:
AR to GL Reconciliation Report
Parameters:
Output:
Unapplied Receipts Journal

Parameters:
Output:
Receipts Journal
Parameters:
Output:
Receipt Register
Parameters:
Output:
Unposted Items Report

Parameters:
Output:
Subledger Period Close Exceptions Report

Parameters:
Output:

Parameters:
Output:
Assets
Calculate Gains and Losses
Parameters:
Output:
Asset not assigned to any Cost Centre Listing

Parameters:
No Parameters
Assignment without CC "forbidden"
Output:
Journal Entry Reserve Ledger / Tax Reserve Ledger Report

These reports are generated automatically during the "Run Depreciation" process,
dependant upon if this process runs for the Corporate- or the Tax book
Parameters:
Output:
Cost Detail and Cost Summary Report

Cost Detail Report
Parameters:
Output:
Cost Summary Report

Parameters
Output
Parameters
Output
Revaluation Reserve Detail and Revaluation Reserve Summary Reports

Parameters:
Output:
Reserve Detail and Reserve Summary Reports

Parameters:
Output:
Revaluation Reserve Detail and Revaluation Reserve Summary Reports

Parameters:
Output:
Asset Additions Report

Parameters:
Output:
Cost Adjustments Report

Parameters:
Output:
Asset Reclassification Report

Parameters:
Output:
Asset Transfers Report

Parameters:
Output:
Asset Retirements Report

Parameters:
Output:
Output
Reinstated Assets Report

Parameters
Output
Cost Clearing Reconciliation Report

Parameters:
Output:

Parameters:
Output:
Unposted Journal Entries Report

Parameters:
Output:
Asset Additions By Cost Centre Report

Parameters:
Output:
Asset Additions Responsibility Report

Parameters:
Output:
Asset Disposals Responsibility Report

Parameters:
Output:
Asset Inventory Report

Parameters:
Output:
Asset Retirements by Cost Centre Report

Parameters:
Output:
Responsibility Reserve Ledger Report

Parameters:
Output:
Asset Summary Report (Germany)

Parameters:
Output:
General Ledger
Journals Batch Summary
Parameters:
Output:
Journals - (180 Char)

Parameters:
Output:
Journals - Entry
Parameters:
Output:
Journal - Lines
Parameters:
Output:
General Ledger - Entered Currency

Parameters:
Output:
Journals - Document Number

Parameters:
Output:
Subledger Period Close Exceptions Report

Parameters:
Output:
Trial Balance
Parameters:
Output:
Trial Balance - Detail

Parameters:
Output:
Trial Balance - Expanded

Parameters:
Output:
Account Analysis (180 Char)

Parameters:
Output:
Profit and Loss (example FSG report)

Parameters:
Output:
Balance Sheet (example FSG report)

Parameters:
Output:
CLE: Journal Details Report

Parameters:
Output:
VAT Reconciliation
The following section describes the reconciliation process for input taxes und output
taxes in the Oracle E-Business Suite R12.
Procedures
The following steps need to be performed before the reconciliation of the input /output
taxes can be done.
Important: Before starting the tax reconciliation all accounting entries
from the Subledgers need to be transferred into GL and posted in GL
1. CLE: Germany VAT Detail Reconciliation Report

The first step is to run the report "CLE Germany VAT Detail Reconciliation Report".
Parameters:
Output:
This report will show all input tax und output tax amounts, the tax accounts, and the
revenue and liability accounts.
To reconcile the output tax the tax amount from row "Tax Class Total" for Tax Class
"Output" needs to be compared with the actual output tax value booked in GL.
To reconcile the input tax, the tax amount from row "Tax Class Total" for Tax Class
"Input" needs to be compared with the actual input tax value booked in GL.
If the amounts are the same, then the report "CLE: Germany Preliminary VAT
Declaration Report" can be started. This report provides all the necessary information to
fill out the "VAT Declaration Form".
If the amounts are not the same, the following reports can be started for further
reconciliation analysis "CLE: VAT Transactions With Difference Report" and "CLE:
German VAT Detailed Transaction Report (1)" (section 3 and 4 of this chapter).
2. CLE: Germany Preliminary VAT Declaration Report
Parameters:
Output:
The report "CLE: Germany Preliminary VAT Declaration Report" provides all necessary
information to fill out the VAT Declaration Form. The row numbers, column numbers
and the column tax of the "CLE: Germany Preliminary VAT Declaration Report"
represent the row number, the base for tax and the tax amount of the VAT Declaration
form.
VAT Declaration form:
3. CLE: VAT Transactions With Difference Report

Parameters:
Output:
The report "CLE: VAT Transactions With Difference Report" shows differences on a
transactional level between the booked tax amount on the transaction and the
computed tax amount.
4. CLE: German VAT Detailed Transaction Report (1)
Parameters:
Output:
The report "CLE: German VAT Detailed Transaction Report (1)" shows all transactions
booked in AP, AR and GL. This report is used together with the Oracle standard report
"Account Analysis Report" for analysis and identification of possible differences.
CLE: German VAT Detailed Transaction Report (1)
CLE: Germany Preliminary VAT Declaration Report

Parameters:
Output:
CLE: VAT Transactions With Difference Report

Parameters:
Output:

Index
Symbols
General Controls/Cash Clearing, 2-23
A
Account Analysis (180 Char), 6-67
Account Analysis Report, 5-4, 6-4
Accounting Flexfield (Kontoflexfelddetails), 4-1
Accounting Sequencing, 2-2
Accounting Setup Manager: Subledger
Accounting Options, 2-6
Accounting Setup Manager: Suspense
Accounting , 2-7
Account Merge , 4-6
Adding Costs to an existing Asset, 3-17
Allow Amortized Adjustments, 2-36
AP, 4-2
AP/AR-Netting, 3-9
AP Period (Periodenstatus), 4-2
AR, 4-4
AR Period (Periodenstatus), 4-4
AR System Parameters (Debitorenoptionen), 4-4
AR to GL Reconciliation Report, 6-21
Asset Additions By Cost Centre Report, 6-48
Asset Additions Report, 6-39
Asset Additions Responsibility Report, 6-49
Asset Books, 2-37
Asset Book Setup (Afa Buch Setup), 4-6
Asset Categories Setup (Anlagegruppensetup), 46
Asset Disposals Responsibility Report, 6-50
Asset Inventory Report, 6-51
Asset not assigned to any Cost Centre Listing, 6-
29
Asset Numbering, 3-17
Asset Prorate Convention Rules, 4-7
Asset Reclassification Report, 6-41
Asset Retirements by Cost Centre Report, 6-52
Asset Retirements Report, 6-43
Assets, 2-36, 3-17, 5-18, 6-28
Assets, Asset numbers, Asset Categories, 4-9
Assets and Asset books , 4-7
Assets and Asset Description, 4-8
Assets Asset Distributions, 4-10
Asset Summary Report (Germany), 6-54
Asset Transfers Report, 6-42
Audit Trail, 4-1
Audit Trail Report , 4-12
B
Balance Sheet (example FSG report), 6-69
Balances Reports, 5-22
Bank Definition, 2-17
Banking Model, 2-16
Banking Setup, 2-16
Bank Statement Detail Report, 6-1
C
Calculate Gains and Losses, 6-28
Cash Management, 5-1, 6-1
Changing APPS Password, 2-1
Changing seeded asset details, 3-18
Check Digit, 2-23
(1), 6-75, 6-77
Index-1
CLE: Germany Preliminary VAT Declaration

Report, 6-73, 6-77
CLE: Journal Details Report, 6-70
CLE: VAT Transactions With Difference Report ,
6-74, 6-78
Collections, 2-35
Collections Strategy, 2-36
Complete Daily Cash Management Activities, 5-1
Considerations, 2-1
Cost Adjustments Report, 6-40
Cost Clearing Reconciliation Report, 6-45
Cost Detail and Cost Summary Report, 6-31
Create a Customer Bank Account, 2-27
Create an internal bank account, 2-20
Create a supplier bank account, 2-25
Create Bank Statement Cash flows, 5-2
Create Miscellaneous Transactions , 5-2
Cross Payables/Receivables, 3-9
Customer Account Merge, 3-5
Customer Bank Account Data, 3-5
Customer Bank Account Data (Bankdaten), 4-5
Customer Duplications, 3-5
Customer Header & Site Information
(Kundenheader und site Informationen), 4-4
Customer setup considerations, 2-16
D
Define a bank branch, 2-18
Define Tables to be Audited, 4-1
Delinquency, 2-35
Depreciation calculation according to 7 II
Einkommenssteuergesetz (EStG), 3-17
Depreciation Methods of an Asset
(Abschreibungsmethoden einer Anlage), 4-7
Depreciation Projections, 5-21
Disbursement Options, 2-32
Discount Invoices/Credit Memo fully applied, 34
Discount Partial Payments, 3-4
Document Sequencing, 2-2
Dunning plan, 2-36
F
FA, 4-6
Format Payment Instructions , 3-15
Freeze Journals, 3-3
Functional Setup, 4-11
Fund Capturing, 3-16
Funds Capturing Process, 2-33
Funds Capturing Setup, 2-33
Funds disbursement, 3-10
Funds Disbursement Setup, 2-31
G
General Ledger, 2-2, 3-1, 5-23, 6-57
General Ledger - Entered Currency, 6-61
General Ledger Reconciliation Report, 6-3
General Ledger Reports, 5-22
Generate Sweep Transactions, 5-1
GL, 4-1
GL Period (Periodenstatus), 4-1
I
IBAN CODE, 2-23
Invoice GL-Date Mechanism, 3-4
Invoice Printing, 3-8
Invoices on Hold Report, 6-5
J
Journal Batches, 5-26
Journal Entries Report, 6-6
Journal Entry Report, 6-20
Journal Entry Reserve Ledger / Tax Reserve
Ledger Report, 6-29
Journal - Lines, 6-60
journal Reconciliation, 5-28
Journals - (180 Char), 6-58
Journals Batch Summary, 6-57
Journals - Document Number, 6-62
Journals - Entry, 6-59
Jurisdictions, 2-41
EBusiness Tax , 2-38

E-Business Tax Setup Regime to Rate flow, 2-38
Exchange Rates (Wechselkursnderungen), 4-2
Ledger/Ledger Set Changes (Ledger/Ledgerset

nderungen), 4-2
Ledger Architecture, 2-3
Index-2
Ledgers, 2-3
Ledger Sets, 2-3
Load Bank Statements, 5-1
Localized Asset Summary Report, 3-18
M
Manage Payment Documents, 2-24
Manual Journal entries with VAT, 3-1
MultiOrg Access Control, 2-5
N
New Localizations R12, 3-18
O
Open Account AP Balance Listing Report, 6-13
P
Party Merge , 4-5
Patch Level, 3-1
Payable Options, Single Payment, Allow
Pre-Date, 3-4
Payable Options Curreny, 2-10
Payable Options Invoice , 2-11
Payable Options Payment, 2-11
Payables, 2-9, 3-4, 5-4, 6-5
Payables Options - Discount, 2-9
Payables Options Interest , 2-11
Payables System Setup, 2-9
Payables to General Ledger Posting process, 5-7
Payee, 2-34
Payment File Accompanying Letter, 3-15
Payment Methods, 2-31, 2-33
Payment Process, 2-31
Payment Process Requests, 3-12
Payment Register, 6-8
payments, 2-28
Payments, 3-10
Payments Schedules Report, 3-14
Payments Setup - Overview, 2-28
Payment System, 2-30
Posted Invoices Register, 6-12
Posted Invoices Register , 5-8
Posted Payments Register, 5-8
Post to General Ledger , 5-3
Prepayments ISTversteuerung von
Anzahlungen, 3-6
Procedures, 5-1
Profile Options, 2-6
Profit and Loss (example FSG report), 6-68
Prorate Expense, 2-10
Prorate Tax, 2-10
R
Receipt Overapplication, 3-9
Receipt Register, 5-14, 6-24
Receipts Journal, 6-23
Receipts Journal Report , 5-14
Receivables, 2-11, 3-5, 5-10, 6-16
Recommendations , 2-1
Reconcile Bank Statements, 5-2
Reconcile Oracle Payables Activity , 5-8
Reconcile Receipts, 5-14
Reconcile the Journal Import Process, 5-16
Reconciliation Process, 5-1
Refunds, 3-9
Reinstated Assets Report, 6-44
Reserve Detail and Reserve Summary Reports, 635
Reserve Ledger Reports, 5-22
Resolve Un-reconciled Statement Lines, 5-3
Responsibility Reports, 5-23
Responsibility Reserve Ledger Report, 6-53
Retirement Accounts, 2-37
Revaluation Reserve Detail and Revaluation
Reserve Summary Reports, 6-34, 6-38
Rollback Depreciation , 5-21
Rules, 2-43
Run Bank Statement Detail Report, 5-3
Run Calculate Gains and Losses , 5-18
Run Depreciation, 5-19
Run the GL Reconciliation Report , 5-3
Run Transactions Available for Reconciliation
Report , 5-3
S
Sales Journal by Customer , 6-18
Sales Journal by Customer Report and the Sales
Journal by GL Account Report, 5-11
Sales Journal by GL Account Report, 6-19
Scoring Engines and Scoring Components, 2-35
Security Profile, 2-5
Index-3
Setting up Asset Books , 2-36

Setup, 2-1, 2-5
Setup Payables Options, 2-9
Setup Recommendations and Related
Considerations, 2-1
Setup VAT for adjustments, 2-14
Shared Payments Setup, 2-29
Specific Rule Setup for Payable / Receivable Tax
Separation, 2-44
Standard Journal reports, 5-25
Status, 2-40
Subledger Accounting Method, 3-1
Subledger Accounting Program Report, 5-8, 6-9
Subledger Period Close Exceptions Report, 6-26
Supplier Bank Account Data, 3-5
Supplier Bank Account Data (Bankdaten), 4-3
Supplier duplications, 3-5
Supplier Header & Site Information
(Lieferantenheader und site Informationen), 4-3
System Account, 2-10
System Administration, 2-1
System Options, 2-12
System Profile Options, 2-11
T
Taxes, 2-39
Tax regimes, 2-38
tax reports, 5-30
Templates, 3-11
Third Party Control Accounts , 2-7
Transaction Register, 6-16
Transaction Register , 5-11
Transaction Reports , 5-22
Transactions, 2-35
Transactions Available for Reconciliation Report,
6-2
Transmission Configuration, 2-29
Trial Balance, 6-64
Trial Balance - Detail, 6-65
Trial Balance - Expanded, 6-66
U
Unaccounted Transactions Report, 6-7
Unapplied Receipts Journal, 6-22
Unplanned Depreciation and Cost Adjustments,
3-17
Index-4
Unposted Items Report, 6-25

Unposted Journal Entries Report, 6-47
User Password Changes, 2-2
V
VAT Declaration form, 6-74
VAT Reconciliation, 6-71
W
Web ADI Journal Entries, 2-8
Work Queue, 2-35

R12 Implementation Recommendations For Germany (February 2010) E15627-01

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

R12 Implementation Recommendations For Germany (February 2010) E15627-01

Transféré par

Droits d'auteur :

Formats disponibles

Oracle E-Business Suite

Implementation Recommendations for Germany

Oracle E-Business Suite Implementation Recommendations for Germany, Release 12

Send Us Your Comments

Setup Related Recommendations and Considerations

Process Related Recommendations and Considerations

Cross Payables/Receivables...................................................................................................... 3-9

Are the implementation steps correct and complete?

Deaf/Hard of Hearing Access to Oracle Support Services

Accessibility of Code Examples in Documentation

Accessibility of Links to External Web Sites in Documentation

Related Information Sources

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

1-2 Oracle E-Business Suite Implementation Recommendations for Germany

Definition of Roles and Responsibilities

Assignment of Setup functions to Roles/Responsibilities

Initiate Setup documentation

Update Setup documentation

Setup Related Recommendations and Considerations 2-1

User Password Changes

2-2 Oracle E-Business Suite Implementation Recommendations for Germany

Accounting Sequence elements:

should be renewed on a fiscal year basis.

Setup Related Recommendations and Considerations 2-3

Ledger Sets can be used for different functions such as:

2-4 Oracle E-Business Suite Implementation Recommendations for Germany

MultiOrg Access Control

Setup Related Recommendations and Considerations 2-5

Security List Maintenance

to derive a complete list of your organizations when using MOAC.

MO: Security Profile

MO: Default Operating

Accounting Setup Manager: Subledger Accounting Options

Summarized by GL-Date Period

2-6 Oracle E-Business Suite Implementation Recommendations for Germany

Accounting Setup Manager: Suspense Accounting

Third Party Control Accounts

Liability account, used in AP for transactions

Receivables Account, used in AR for transactions

Asset Clearing Account

Setup Related Recommendations and Considerations 2-7

Web ADI Journal Entries

2-8 Oracle E-Business Suite Implementation Recommendations for Germany

Payables Options - Discount

Setup Related Recommendations and Considerations 2-9

There are three different discount methods available:

Use Multiple Currencies

Define the Accounts for

Account for Realized Gains

Account for Realized Loss

2-10 Oracle E-Business Suite Implementation Recommendations for Germany

Account for Rounding

Payables Options Invoices

Payables Options Interest

Allow Interest Invoices

Payables Options Payment

Exclude Tax from Discount Calculation

Setup Related Recommendations and Considerations 2-11

These system profile options should be set up as follows:

AR: Application GL Default

Later of Current date, Receipt and Invoice GL

AR: Cash - Allow Actions

AR: Change Customer on Transaction