Professional Documents
Culture Documents
Financial accounting is concerned with the preparation of financial statements for decision
makers such as stockholders, suppliers, banks, government agencies, owners and other
stakeholders. The fundamental need for financial accounting is to report the results to
interested users. Treasury Management is fast emerging as a specialization in many
companies and the accounting function is being delinked from the finance function. Oracle
Treasury helps you meet the critical planning, processing, and reporting requirements of
global treasury operations. Correctly accounting for treasury transactions is of great
importance because of the impact on your organization’s financial results. This becomes
more pronounced for Treasury as it involves cash flows.
Oracle Treasury has the ability to automatically generate accounting entries and pass them
seamlessly to Oracle General Ledger. This process comprises the following four steps:
You can post journal entries for cash flow amounts (that is, non-revaluation and non-accrual
journal entries) on a daily or weekly basis, and post journal entries for your
revaluation/accrual deals on a separate timeline. The posting of cash flow amounts does not
require performing revaluations or generating accruals prior to generating daily journals.
Before creating the accounting entries, the following setup needs to be in place. The setup
should be complete and correct in all respects to ensure that the accounting is generated
comprehensively. Hence it is of utmost importance that the setup is made properly. In this
section we will discuss:
1. Setup Company profiles
2. Setup System parameters
3. Setup Journal entry actions
System parameters define settings for the operation and control of Treasury and are usually
set at the time of implementation. You can update them after implementation as needed. For
the purposes of accounting we review the following parameters.
The Journal Entry Actions window accessed through the form Setup->System->Journal
Entry Actions helps to define the General Ledger accounts that are used to generate
accounting entries for each combination of deal type, deal subtype, product type, and
portfolio within a company. To ensure a balanced ledger, it is critical that accounts and
journals are set up completely and correctly. This screen has the following tabs:
1. GL Accounts.
2. Intercompany Accounts.
3. Journal Structures.
4. Query by GL Account.
5. Copy GL Accounts.
GL Accounts
The GL Accounts tabbed region is used to define General Ledger accounts for each
company. You can add new accounts and review existing accounts, but you cannot change
or delete existing accounts in this form. The available General Ledger accounts derive from
the set of books associated with the company. If you want to define a new General Ledger
account, enter a General Ledger account alias in the GL Account column. Treasury
populates the fields with the General Ledger account number and description. In the
Treasury Reference field, you can enter your own description to identify this GL account.
The Treasury reference that you enter appears alongside the GL account number in the list
of values throughout Treasury.
Use the Journal Structures tabbed region is used to set up the actual journal structure. Here
you define for each applicable company name, the daily journal entries that you want to
generate automatically for each combination of deal type, deal subtype, product type, and
portfolio. You must update journal entries whenever you create a new product type or
portfolio or when you unauthorize a product type.
Firstly query the first Deal Type, Deal Subtype, Product Type and Portfolio combination
that you want. If the journal values do not appear for the selected combination, you can
copy values from another combination that has the same deal type by placing your cursor in
the Date Type field and choosing the Copy Journal Details button. Enter or change the Date
Type, Amount Type, and Action Code as required. If you want the journal action to refer to
the general ledger number related to the company's cash flow bank account, select the Bank
GL check box. Otherwise, enter an account number in the GL Account field. If this is an
intercompany funding deal, direct journal actions to either the principal or the interest
General Ledger account number by selecting the Prin GL or the Int GL check box. These
check boxes are only available for non-accrual and non-revaluation date types. Identify the
action as a Debit or Credit. If necessary, enter the effective dates for this journal action. You
can enter a future date in the ‘Effective From’ field to pre-define a journal action. You can
use the ‘Effective To’ field to deactivate a journal action after the date you specify.
Oracle Treasury creates journal entries for brokerage fees also. Setting up date type-amount
type combinations does not do this. There is a screen on the brokerage setup form to assign
GL account. This is where the GL accounts for journal entries are determined. The
offsetting GL account is derived from the cash GL account on the bank account out of
which the fee is settled. Note that brokerage fees are journalized only after they are settled
(authorized for settlement).
Query by GL Account
You can review the deal combinations that were set up for a specific General Ledger
account. To do this enter the company code of the company whose General Ledger account
you want to review and choose the Query by GL Account tab. The Find GL Accounts
window appears. Select a General Ledger account and choose the Find button. The journal
entry actions for that General Ledger account appear.
If you are setting up several companies with similar sets of journals, you can copy a set of
journals from a company you have already set up. To copy a general ledger account, enter
the company code of the company you are setting up and choose the Copy GL Accounts
tab. In the Copy From Company field, select the company that has the journals you want to
copy and then choose the Copy Journals button. Update the appropriate General Ledger
accounts and the effective dates.
The following are sample treasury accounting configurations for illustration purposes only.
In many cases, the following accounting templates have not been fully tested and may not
produce journal entries that are 100% correct. Also, these journal structures may not satisfy
your unique accounting requirements or cover all possible scenarios. You should use this
only as an example of one possible set up and thoroughly test whatever final configuration
you define. Oracle does not intend to imply that following these sample set ups will result in
proper accounting entries for your company.
Date Type
Amount Action Bank Debit/Credit GL Account
Type Code GL
REVAL UNREAL GAIN Db Liability Account
REVAL UNREAL GAIN Cr Unrealized Gain/Loss
REVAL UNREAL LOSS Db Unrealized Gain/Loss
REVAL UNREAL LOSS Cr Liability Account
ACCRUAL INTADJ POS Db Interest Income/Expense
ACCRUAL INTADJ POS Cr Accrued Interest
SETTLE INTSET Db Accrued Interest
SETTLE INTSET * Cr
DEALT INITIAL INCRSE Db Clearing Account
DEALT INITIAL INCRSE Cr Liability Account
COMENCE INITIAL INCRSE * Db
COMENCE INITIAL INCRSE Cr Clearing Account
COMENCE PRINFLW INCRSE * Db
COMENCE PRINFLW INCRSE Cr Liability Account
COMENCE PRINFLW DECRSE Db Liability Account
COMENCE PRINFLW DECRSE * Cr
REVAL CCYREAL GAIN Db Liability Account
REVAL CCYREAL GAIN Cr Currency Gain/Loss
REVAL CCYREAL LOSS Db Currency Gain/Loss
REVAL CCYREAL LOSS Cr Liability Account
Deal Type IRS - Interest Rate Swap (Should be similar to TMM - Wholesale Term
Money)
Subtype INVEST
Date Type
Amount Action Bank Debit/Credit GL Account
Type Code GL
COMENCE COMENCE * Credit
COMENCE INT Credit Mkt. Securities Contra -
Unamortized Discount
COMENCE INTL_FV Debit Marketable Securities
ACCRUAL <EFFINT> POS Debit Mkt. Securities Contra -
Unamortized Discount
ACCRUAL <EFFINT> POS Credit Interest Income
REVAL UNREAL GAIN Debit Mkt. Securities Contra -
Gain/Loss
REVAL UNREAL GAIN Credit OCI Gain/Loss
REVAL UNREAL LOSS Credit Mkt. Securities Contra -
Gain/Loss
REVAL UNREAL LOSS Debit OCI Gain/Loss
REVAL REAL GAIN Credit Mkt. Securities Contra -
Gain/Loss
REVAL REAL LOSS Debit Mkt. Securities Contra -
Gain/Loss
REVAL REAL GAIN Debit OCI Gain/Loss
REVAL REAL GAIN Credit Other Income (Expense)
REVAL REAL LOSS Credit OCI Gain/Loss
REVAL REAL LOSS Debit Other Income (Expense)
MATURE BAL_FV * Debit
MATURE BAL_FV Credit Marketable Securities
Date Type
Amount Type Action Bank Debit/Credit GL Account
Code GL
COMENCE COMENCE * Debit
COMENCE INTL_FV Credit Marketable Securities
COMENCE <DISCREV> Debit Mkt. Securities Contra -
Unamortized Discount
When running the accounting process you can choose to generate journals of two kinds:
• Non-Revaluation/Non-Accrual Related Journal Processing
• Revaluation/Accrual Related Journal Processing
The second batch type is called "Revaluation/Accrual Related Journals" and it creates
journal entries for all amounts ("cash", revaluation, accrual). The pre-requisite for this type
of a journal batch is, thus, the creation of Revaluation and/or Accrual batch. If you select
this batch type in the Batch Source region, then you will be required to enter a Batch ID that
has been generated when you finished running Revaluation and/or Accruals.
Accounting Batches
You start the accounting process by creating an accounting batch. An accounting batch
consists of a batch ID, a batch period (date range for the transactions included in the batch),
and a set of transactions that fall within the batch period. You can create an accounting
batch and generate journals in one step for non-revaluation and non-accrual journal entries.
If you are performing revaluations and/or generating accruals, then after you create an
accounting batch, you must authorize the batch at each step of the accounting process. For
example, once you complete revaluations you must authorize the batch before you can begin
accruals for that same period. Similarly, the accruals batch must be generated and authorized
before you can generate any journals for that date range. You cannot change or delete an
authorized accounting batch because it may affect the accounting process. If you have
authorized the revaluations and accruals for a batch, you can only delete the batch or make
any changes to the revaluations for the batch after you unauthorize both the revaluations
and accruals. If you want to make changes to the accruals, you must first unauthorize the
accruals. Once a batch has been transferred to General Ledger, you cannot unauthorize,
make changes, or delete the batch.
The table below lists the statuses that must exist before you can change or delete an
accounting batch. For example, if you want to change revaluations for an accounting batch,
the batch can have revaluations generated for it but the revaluations cannot be authorized.
Batch Periods
The start and end dates of the batch period are automatically populated based on the end
date of the previous batch and the length of the periods that are defined in the company
accounting calendar. Typically a period is one month. You can edit the period end date as
required. For example, you can create a batch period of one day or two weeks in length. The
first time you create a batch, the start date for the batch period is the date of the oldest
transaction and the end date is the current system date. The dates covered by batch periods
must be consecutive, unique and gapless. Each date must appear in a batch, and the same
date cannot appear in two different batches. For example, if you create a batch for the
period June 1 to June 15, you cannot create another batch for the period June 1 to June 30,
or start the next batch on June 17. Instead, you must either create another batch that covers
all of the remaining dates (for example, a batch for June 16 to June 30) or delete the existing
batch and create a new batch that covers all of the dates (June 1 to June 30).
Revaluations
Revaluation is the process of adjusting the rates and prices of your financial instruments to
reflect the current market value and calculate the realized or unrealized profit and loss. This
is an optional step in the accounting process and is the first step only if the Accounting -
Perform Deal Revaluations company parameter is set to Yes. If this option is set to No, the
accounting process typically starts with Accrual. The rates that you capture to revalue your
financial instruments (interest rates, bond and stock prices, foreign exchange spot rates, or
volatility rates) are collectively called revaluation rates. Revaluation rates are captured from
the Current System Rates window for the specified batch period.
To perform revaluations, firstly define the start and end dates for the accounting batch
period. Usually this maps to a single month but can encompass a longer period. The ‘Period
From’ cannot be changed but the ‘Period To’ can be altered. Now click on the button
Deal pricing models are predefined for each deal type. You can define new pricing models
for any deal type that has a Fair Value pricing model. If the pricing model is fair value, you
will need to specify the override value and override type in the revaluation window. Here is
the list of the revaluation methods used for each financial instrument in Oracle Treasury.
Accruals
Use the Accruals window to authorize the accruals for your batch. You can generate
amortizations and accruals adjustments, split by revenue and expense, for all money market
products. These adjustments include amounts for settling derivatives, such as FRAs and
options. Amortization and accruals adjustments are calculated for each batch period, rather
than as an accumulating amount for multiple periods. Reversal entries are not required.
The accrual methods calculate the accounting period discount by multiplying the Yield to the
Maturity rate at the time of purchase, and by multiplying that to the beginning accounting
period cost basis. Accruals is the first mandatory step in the accounting process. If your
company set the Accounting - Perform Deal Revaluations company parameter to ‘Yes’, then
1. Define the start and end dates for the batch, unless the batch is already defined.
2. Create the period adjustments for the accrual.
3. Authorize the accrual for the batch.
4. You can adjust the accruals for a batch up until the point when you transfer your
daily journals to General Ledger.
Use the Daily Journals window to generate the daily journals for an accounting batch, view
the generated journal entries, change the dates or GL accounts for your journal entries and
reallocate suspense journal entries to a GL account. Daily journals are generated based on
the deals in the accounting batch and the journal entry actions that you set up in the Journal
Entry Actions window. Daily journals are generated using the transaction foreign currency
and set of books currency equivalent.
In the "Submit Process to Generate Journals" form, which you see after clicking on the
"Generate Journals" button in the "Daily Journals" form, there are two types of journal
batches that you can generate. (Note: all accounting in Treasury is done in "batches" that
span over a user-defined period of time and cover all eligible deals). The default value is
"Generate Non-Revaluation/Non-Accrual Related Journals".
Refer to the following screenshots for the steps to generate daily journals.
Use the Maintain/Review Journal Details window to view daily journals or change generated
journal entries. You can only change generated journal entries for daily journals that have not
been transferred to General Ledger. Please note that if you set the ‘Validation Required for
Accounting’ system parameter to ‘Yes’, then the accounting batch process only creates
journals for validated transactions. The accounting batch log file records the
revalued/accrued and non-revalued/non-accrued transactions that are not validated and
therefore did not have journal entries created. If the batch creates journal entries for
revalued and accrued transactions but related cash transactions are not validated, the log file
indicates the creation of unbalanced journal entries. To correct unbalanced journal entries
you must rollback the journal entries created, validate the relevant transactions, and run a
new accounting batch. Updating the Journal Date is subject to these restrictions:
1. You cannot enter a date on which there is no daily exchange rate available in your
company's exchange rate type between the transaction currency and the SOB
currency.
2. You cannot enter a date that falls within a closed GL period.
If you want to reallocate entries from a company suspense journal to a General Ledger
account, use the Suspense Journals window.
After successfully completing all of the steps in the accounting process, transfer your daily
journal batches to General Ledger. Before you perform this step, you must ensure that you
have entered and verified all accounting changes. Once a batch has been transferred to
General Ledger, you cannot unauthorize, make changes, or delete the batch. If a deal
changes after you transfer to GL, you must create a reversal and a replacement journal.
If your journal batch contains entries with journal dates that fall into a closed GL period,
you can optionally post these entries to the next open GL period. If you choose this option,
Treasury maintains a record of both the actual journal date and the new posting date. You
can choose to allow the transfer of unbalanced journals to GL by setting the company
parameter ‘Accounting - Allow Unbalanced Journal Transfer (Yes/No)’ in the Company
Profiles window.
Daily journals are transferred to General Ledger in both the transaction currency and the set
of books currency equivalent. The rate used to calculate the set of books currency equivalent
is drawn from the GLRATES table. This calculation takes place when you generate daily
journals.
Transferring Options
There are two places in the system where XTR journals can be summarized.
First, there is a company level parameter "Accounting - Journal Transfer Method" (Detail or
Summary). It should be noted that it only takes effect during journal transfer. Even if the
value of the parameter is set to "Summary", the journals that are going to be generated in
XTR and be visible in the Daily Journals form will always represent individual deals. In other
words, if there are 2 deals in the system that on the same date should each generate a debit
to the same GL account, you will see these deals as two separate debit lines in the Daily
Journals form.
Once you go to the Transfer Journals form and pull up the journal batch, this is when the
system will look at the company level parameter and either shows you two separate debits
Since you can view XTR journals in Daily Journals form even after the transfer to GL, the
transferred journal lines will always be displayed as individual - not summarized - journal
entries (even if you transferred them as summary journals). It is important to note that XTR
summarizes debit and credit journals separately during transfer using the following
parameters:
And this is transferred using the Summary method, in the GL interface table the following is
seen after the transfer:
Now, when the XTR journals are transferred to GL, they are placed in the GL interface
table. Before you can post them, you have to import them from the GL interface table into
the main GL table. This is the second place where the journals can be summarized.
• For this particular XTR journals batch, take note of all journal entries in the batch on
the XTR side (Daily Journals form), their amounts, GL accounts, dates and dr/cr
side
• Group all entries by GL account and for each GL account calculate total debits, total
credits and the net of debits and credits.
• Verify that netting debits and credits for the same GL account results in the
calculation of the same total debit and credit amounts that the client sees in GL after
import.
If you have already run revaluation and accruals for a month and later enter transactions for
a month you will see the following messages that are intended.
1. Setup the Journal Entry Actions (Setup-> System -> Journal Entry Actions)
2. Create an ONC deal Money Market Transactions -> Short Term Money)
Report Parameters
Company this lists all the treasury companies you have access to as defined by the User
Access Level. If the field is left blank, the system processes all treasury companies that you
have access to.
Batch End Date is the batch ending date and the default is the current system date.
Start Process From is the starting point for the accounting process. The choices are:
End Process After is the ending point for the accounting process. The choices are:
• Revaluations: End process after revaluation details are authorized. This value can be
selected if the Start Process From is Revaluations.
• Accruals: End process after accrual details are authorized. This value can be selected
if the Start Process From is Accruals or Revaluations.
• Daily Journals - Generation: End process after journals are generated. This value can
be selected if the Start Process From is Daily Journals - Generation, Accruals, or
Revaluations.
• Daily Journals - Transfer to GL: End process after journals are transferred. This
value can be selected for any of the Start Process From options.
Journals in Closed Periods: Sets the method to handle journal entries that fall into a closed
period. This field is enabled only if the End Process After parameter is set to Daily Journals -
Transfer to GL. The choices are:
• No change: The transaction details are left as is and are transferred to General
Ledger.
• Next open: The journal entries are placed in the next open period and then
transferred to General Ledger.
A feature referred to as "Flexible Journals" has been introduced in 11.5.9 (patch 2428924)
due to the customer demand to process cash-related journals more frequently than accrual or
revaluation related journals. This feature provides the ability to create journal (for Cash-
related amounts only) at any time without the link to the revaluation and accrual batches. In
the Flexible Journals feature, you may be able to generate multiple Cash related (Non-accrual
/ Non-revaluation) batches within the same date (cut off date) provided cash flow
transactions are created after the generation and transfer of the earlier batch. System shall
pick up any unprocessed transaction since the last run and create a new NR/ NA batch with
the same end date. This way multiple transfers could be done within a same day.
The crux of the FAS 133 (and its European counterpart IAS 39) is a special accounting
treatment of gains and losses of qualifying derivatives. Oracle Treasury from the very
beginning was providing support for derivatives, fair value gain/loss calculations (through
Revaluation) and flexible accounting setup. Someone who is very well familiar with the
requirements of the standards and Oracle Treasury functionality can create a FAS/IAS
compliant accounting setup given the three above-mentioned components of the system.
However, some of the steps would still have to be performed manually (effectiveness testing
and reclassification). Oracle Treasury allows you to view your Oracle AP and AR
outstanding exposures real-time and set up relationships to hedge those exposures with FX
forwards. Functionality as of release Financials Family Pack E (XTR.L) allows using only FX
forwards as hedging instruments. If an FX forward deal is designated as an instrument in a
current hedge relationship, cancellation, rollover or predelivery of the deal will result in
cancellation of the hedge relationship.
Oracle Treasury supports the most important building blocks of IAS39 compliance: mark-
to-market revaluation and breakdown of revaluation results into components such as fair
value gain/loss (due to the change in the market price of the instrument) and currency
gain/loss (due to the change in the exchange rate between your SOB currency and the
currency of the instrument). Oracle Treasury uses internationally accepted pricing models to
calculate fair value gains/losses of all the financial instruments supported, derivative and
physical alike. Also, Oracle Treasury allows immense flexibility in setting up journal entry
structures based on a variety of user-defined groupings such as portfolios (company/LE
specific) and product types (system-wide). To differentiate the accounts that the gain/losses
of hedge instruments will be booked to, user can set up a portfolio called HEDGE and set
up the journal entry actions such that the gain/losses are booked to a set of GL accounts
other than the normal/non-hedge accounts. Thus, when hedge deals are saved in this
portfolio, the accounting entries will be booked to the desired GL accounts. With the aid of
descriptive fields, it is possible to store any user-defined information on individual deals.
Also, with the attachment functionality, user can attach any soft-copy document or file to
deals or hedge relationships. With the aid of Oracle Discoverer, it is possible to create
reports displaying data recorded at the hedge level.
Foreign Exchange Hedge Effectiveness and Accounting Under IAS 39 and FAS 133
This feature helps to support foreign exchange forward hedging of Payables and Receivables
as defined by IAS 39 and FAS 133. This new feature expands existing functionality that
already allows users to view real-time Payables and Receivables exposures, as well as
designate and track related Foreign Exchange forward hedges. Oracle Treasury now also
automatically calculates the retrospective effectiveness of these hedges, comparing historical
gains or losses of the Foreign Exchange forward contracts to the offsetting losses or gains
associated with the underlying exposures being hedged. Oracle Treasury allocates the
effective and ineffective portions of these revaluation amounts and can automatically
generate proper accounting entries under IAS 39 and FAS 133. This feature also delivers the
ability to audit prospective effectiveness testing results, as well as reclassify the effective
portion, or deferred, gains and losses back into current period earnings when the underlying
exposure is realized.
Hedging is a strategy designed to reduce financial risk using derivative instruments. A hedge
can help lock in profits or limit losses by reducing the volatility of an asset or liability by
mitigating the risk of loss. To use this feature:
1. Setup hedge policies that define the exposure sources (known as hedge items) that
you want to hedge and the financial instruments (known as hedge instruments) that
you want to use to hedge those items using foreign exchange spot/forward deals.
This can be done by opening the form Setup->Policies->Hedge Policies.
For Hedge Item Revaluation, if time value is excluded on the Hedge Strategy form, then GL
Rate model will be used to revalue hedge items (CCYUNRL). If time value is not excluded
on the Hedge Strategy form, then forward Rate model will be used to revalue hedge items
(UNREAL).
Effectiveness Testing
In 11.5.10 CU2, prospective and retrospective hedge effectiveness testing are the two new
(optional) steps in the accounting process. In order to able to test the effectiveness of the
hedge, ensure that the Company Parameter 'Accounting - Perform Hedge Effectiveness
Testing' is set to Yes. This form can be accessed by Setup->Parties->Company Profiles-
>Tab Parameters.
Retrospective
This is a retrospective looking statement that in the past the hedge was effective (historical
gain/loss offset analysis). Here, if the company parameter is set to ‘Yes’, this process
becomes a required step after revaluations in the accounting batch. This process splits
unrealized gain/loss amounts of deals designated as hedge instruments into effective and
ineffective amounts according to test results, as well as calculates any reclassification amount.
For retrospective testing, there are 5 testing methods that the user can select from at the
hedge strategies setup or hedge attributes level:
1. Shortcut/Fully Effective
2. Period Offset
3. Cumulative Offset
4. Manual Entry
5. No testing
For example if the Derivative/Hedge Instrument Gain is $2200 and the Hedge Item Loss is
$2000, the effectives is 110% (2200/2000). If the tolerance levels are between 80% and
Treasury provides the feature to view the results of the effectiveness testing for both
prospective and retrospective methods. This form can be accessed by View > Hedging >
Effectiveness Test Results.
Retrospective
There is no major change in accounting for Treasury in release 12. Sub ledger accounting
(SLA) is not applicable to Oracle Treasury.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com