Saturday, May 30, 2009

AutoLockbox:

Overview of AutoLockbox:
•Process where customers mail payments to a post office box near
your remittance bank and the bank deposits the payments in your
account at regular intervals.
•Bank provides you with computer files detailing about the receipts
and their application. •Receivables uses Auto Lockbox to import
details about receipts directly into the system.
What is AutoLockbox:
Auto Lockbox is a service that commercial banks offer corporate
customers to enable them to outsource their accounts receivable
payment processing. Auto Lockbox eliminates manual data entry
by automatically processing receipts that are sent directly to
your bank.

Benefits of AutoLockbox:
•Eliminates manual data entry.
•Streamlines the application of receipts to outstanding transactions.
•Effectively manages cash flow by reducing turnover for converting
checks into cash.
•Apply receipts to outstanding invoices
•Import historical receipt data
•Autolockbox reports, such as the Post Quikcash Execution Report,
are a good tool to reconcile autolockbox receipts with the bank
transmission reports.




AutoLockbox is 3 Step Process:

1. Import :During this step, Lockbox reads and formats the data from
your bank file into interface table AR_PAYMENTS_INTERFACE_ALL
using a SQL *Loader.

•Data is imported into interface tables •Imported data does not affect accounts receivables balances
•Import automatically generates the Lockbox Execution Import report
•Use report to check the imported data

2.Validation: The validation program checks data in this
interface table for compatibility with Receivables. Once validated,
the data is transferred into QuickCash tables
(AR_INTERIM_CASH_RECEIPTS_ALL and
AR_INTERIM_CASH_RCPT_LINES_ALL) .
At this point, you can optionally query your receipts in the QuickCash
window and change how they will be applied before submitting the
final step, Post QuickCash script.
•Ensures that each receipt complies with application and customer
requirements
•Customer must have a primary billing location
•Bank can provide a MICR or a customer number to identify customer
•Validated data is transferred to QuickCash tables
•Transfer does not affect accounts receivables amounts
•Receivables can use AutoAssociate or a billing address to identify customer
•Use the Lockbox Execution Import report to review the validation

3.Post QuickCash: This step applies the receipts and updates your
customer’s balances.
•Data is transferred from QuickCash tables to Receivables tables
•Posting updates the account balances to reflect the imported receipts
•View and update receipts in the Receipts window


These steps can be submitted individually or at the same time from the submit Lockbox Processing window. After you run Post QuickCash, Receivables treats the receipts like any other receipts, you can reverse and reapply them and apply any unapplied, unidentified, or on-account
amounts.
MICR Number:
What is a MICR Number:
–Magnetic Ink Character Recognition (MICR)
MICR # Consists of two segments
1st segment - Transit Routing Number (Customer’s Bank) this
identifies the bank from which your customer draws their check.
2nd Segment - Bank Account of the customer (Customer’s Account)
MICR Number Can Only Be Used For One Customer Only!
MICR Number is used to identify the Customer.
The bank account number and the transit routing number makeup
your customer’s MICR number. If a MICR number is shared with
more than one customer, the receipt is rejected.Customers that are
associated must have unique MICR numbers.
By default the lockbox validation program uses an invoice or debit
memo number to determine the customer.

How AutoLockbox Identifies Customers for Receipts:

AutoLockbox can validate your customer data based on the
following attributes . If no match is found, the receipt is imported
as Unidentified receipt. This unidentified receipts can be identified
and then applied from the Quick cash window or the receipt window.

1. Customer Number: If you provide a customer number for
receipts that you import through AutoLockbox, Receivables can
identify the customer to which the receipt belongs .
2. MICR Number: The MICR number that appears on each
receipt relates the customer to a bank. Lockbox only uses MICR
numbers to associate a customer with a receipt if both of the
following are true:
a). The customer number is not included in the transmission
format
b). The MICR number is passed
3. AutoAssociate: If the customer cannot be identified from either
the MICR number or the customer number (for example, if the
transmission does not include this information), you can use
AutoAssociate to determine the customer using matching numbers.
A matching number can be a transaction number, consolidated
billing invoice number, sales order number, purchase order number
or another custom defined number.
4. Associate Receipts with Billing Locations: Receivables also lets
you track receipts for each of your customer’s billing locations.
To use this feature, you must include a billing location in your
transmission format, data file and the flag Require Billing Location
should be set to Yes. This option should be set to yes both at system
options and at the setup of Lockbox. If the box is checked at the
Lockbox, the receipt will be validated only if the billing location is
provided. The setting at the system options level determines
whether Post QuickCash can process receipts with /without billing
locations.

How AutoLockbox Applies Receipts:
If Lockbox is able to identify the customer for a receipt and the
transaction number is provided , Lockbox applies the receipt to this
transaction.
If the transaction number is not provided and Auto associate is
set to Yes, Post QuickCash uses the matching rules defined for the
customer site, customer or Lockbox to apply the receipt.
The setting of Match Receipts By Option tells what type of matching
number is passed in the transmission. If Matching Rules fail, Post
QuickCash applies the receipt using the AutoCash rules set .
If AutoCash rules also fail, Lockbox assigns the receipt a status
of Unapplied. If the transaction number is not provided and Auto
associate is set to No, Post QuickCash assigns the receipt a status
of Unapplied.

AutoLockbox Receipts Matching:
Receivables applies the receipt using:
•Transaction number
•Sales order number
•Purchase order number
•Consolidated bill number
•User-defined number

Maintain Transmission Data:
Use the Lockbox Transmission Data window to delete and edit
transmission data imported into Receivables from your bank
using Lockbox.
You can correct your lockbox data in this window for receipts that fail
validation, then resubmit the validation step again .

Running AutoLockbox:

To Import and apply receipts using AutoLockbox, run each step individually or run them as a group.
Import:
a) If you are importing a new bank file, check the New Transmission check box, then enter a new Transmission Name.
b) If you are resubmitting an existing lockbox transmission, you can select a name from the list of values.
c) Enter the name of the datafile along with path and extension.
d) Enter the name of the control file with out extension. Make sure that
the control file in $AR_TOP/bin directory.
e) Select the transmission Format from list of values.

Validation:

a) Check the Submit Validation Check box.
b) You must enter a lockbox number if Submit Validation is Yes and
the lockbox number is not specified in your bank file.
c) To apply receipts to transactions belonging to unrelated customers,
check the Allow Payment of Unrelated Invoices check box.
d) If you defined your GL Date as ’Constant Date’ in the Lockboxes
window, you must enter a GL Date; if you specified a GL Date of
’Deposit Date’ or ’Import Date’, Receivables uses this as the GL date.
e) Enter a Report Format. Enter ’All’ to include all records processed
in this transmission. Enter ’Rejects Only’ to include only records
that failed validation.
f) To transfer only the lockbox batches in which all records pass the
validation step to the QuickCash tables, check the Complete Batches
Only check box. If you do not check this check box, Receivables will
transfer any receipts within a batch that pass validation, even if
others are rejected.

Post Quick Cash:

a) To apply the receipts and update your Customer’s balances, check
Submit post QuickCash check box.
b)Choose how lockbox should handle invalid transaction numbers.
c) Post Partial Amounts as Unapplied or Reject Entire Receipt

Save your work. Receivables displays the Request ID of your
concurrent process and generates the Lockbox Execution report.

Saturday, May 23, 2009

VSOE and Revenue Recognition

What is Vendor specific objective evidence(VSOE)
==========================================
Vendor Specific Objective Evidence, is Fair Value for Software.
SOP 97-2 was designed for Software companies, and works fairly
well for certain traditional business models.
The concept was introduced in 1997 by the AICPA in their Statement
of Position (SOP) 97-2: It governs how any company that licenses,
sells, leases or otherwise markets software (unless it’s incidental to
the product or service as a whole) must recognize the revenue.

In particular, it governs how companies must recognize revenue from
so-called “multiple-element arrangements” – bundles of software and
related products or services sold as a unit at a single price.

Today, more and more companies find themselves dealing with
VSOE as embedded software becomes an increasingly essential
element in traditionally non-software sectors - consider cell
phones, medical devices, computer networks, even cars with GPS
services, etc.

According to SOP 97-2: you allocate relatively, splitting the fee
amongst the products and related elements based upon VSOE –
which is the price established by the vendor for the separate sale
of each element. Each VSOE price is usually established through
accumulation of a quantity of discrete sales “sufficient” to prove
that the market, in it’s willingness to pay that price, thinks the
price is fair. And here’s the big catch:

You can not recognize revenue for any element either until VSOE
exists for each and every element, or until all of the elements
have been delivered.

Sec's Statement of Postion (SOP) 97-2, Software Revenue

Recognition and SOP 98-9, Software Revenue Recognition with
respect to certain transactions, applied to all entities that license,
sell, lease or market computer software. It specifies that revenue
from an arrangement involving multiple elements should be
allocated to the various elements based on VSOE fair values to
the customer.

Sections of SOP 97-2 were amended with SOP 98-9, Software

Revenue Recognition with respect to certain transactions,
SOP 98-9 states that the residual method of revenue recognition is
required when:
1. There is vendor specfic objective evidence of the fair values of all
undelivered elements in a multiple-element arrangment that is not
accounted for using long-term contract accounting.
2. VSOE of fair value does not exist for one or more of the delivered
elements in the arrangement and 3. All Revenue recognition criteria
in SOP 97-2 other than the requirment for VSOE of the fair value of
each delivered element of the arrangement are satisfied.

Elements of VSOE:
==================

-Software Licenses
- Warranty
- Installation
- Support and professional Services
- Training
Fair Market Value (FMV):
========================

The FASB defined 'fair value' in FAS 159 as "The price that
would be received to sell an asset orpaid to transfer a liability
in an orderly transaction between market participants at the
measurement date. " The key points in this definition are
'orderly transaction' and 'market participants.' Thus fair value
can't be established by looking at an exchange of assets in a
bankruptcy or between 'related parties' as defined by the SEC.

Fair value is established by multiple, non- related market
participants in 'normal, orderly transactions. ' VSOE, on the other
hand, is fair value as established by looking at the historical
transactions of a specific vendor and does not consider what other
vendors are charging for similar products.

Revenue Recognition:

====================
Revenue recognition in today's regulatory and business

environment involves sophisticated revenue scheduling and
allocation, Vendor- specific Objective Evidence (VSOE) carve-outs
and Sarbanes-Oxley compliance. Thus having a common system
for global compliance is key to reducing complexity.
Revenue recognition is a principle prescribing that revenue is
recognized when earned.

It has two considerations - when to recognize revenue, and how
much to recognize. Revenue recognition is relevant for companies
to be able to adhere to legal compliance as per the US GAAP
requirements.

Improper revenue recognition increases the risk of financial
restatement, and financial restatements. Revenue for ISV's is
typically divided into three categories: Software, Maintenance, and
Services. Assuming that software customization is not required,
revenue can be recognized when all of the following criteria are met:

There are four basic criteria that must be met to recognize
revenue
- Evidence
- Delivery
- Fixed or determinable fee
- Collectibility.

Revenue Accounting:
===================
Use the Revenue Accounting feature to quickly and easily adjust

revenue and sales credits at the transaction or line level. You can
make manual adjustments using the Revenue Accounting and
Sales Credits window. Alternatively, use the Revenue Adjustment
API to automatically perform these adjustments. Revenue
Accounting uses the Actions Wizard to guide you through the process
of making and modifying revenue adjustments.
You can also use the wizard to record early acceptance for an

invoice line, if the line is associated with a contract that offers an
acceptance clause.

Invoicing Rules:
===============
Use Invoicing Rules to specify whether to record receivables
amounts in the first (Bill in Advance) or Last (Bill in Arrear)
Period.
Invoicing rules determine when to bill the customer in relation to
the accounting rule Periods. Accounting rules determine the

accounting periods for revenue recognition and Billing.
Two invoicing rules are available:



Bill in Advance: Use this rule to recognize receivables immediately.

Bill in Arrears: Use this rule to recognize the receivable at the end of

the revenue recognition schedule.


•Invoicing rules determine whether to recognize receivables in the first or in the last accounting period.
•Once the invoice is saved, you cannot update an invoicing rule.
•If Bill in Arrears is the invoicing rule, Oracle Receivables updates the GL Date and invoice date of the invoice to the last accounting period for the accounting rule.


Accounting Rules:
=================
Use Accounting Rules to determine when to record revenues.
Accounting Rule determine the number of periods and percentage
of total revenue to record in each accounting period.

Each invoice can have different accounting rule.
Use the Accounting, Fixed Duration type to recognize revenue evenly
over a specific number of periods. Revenue can be spread evenly or a
percentage can be specified for each period.












Variable Duration type to recognize revenue by a percentage for
the first period. The remaining revenue is spread evenly across
the number of periods you specify during transaction entry.

Accounting rules determine when to recognize revenue
amounts. Each invoice line can have different accounting rule.


Oracle Receivables uses the First GL Date field in the Transactions
window to determine when to start recognizing revenue. The number
of periods in which revenue is recognized is determined by the
value in the Number of Accounting Periods field in the Transactions
window.Value defaults from fixed ruleValue must be entered for
variable rule. Accounting distributions are created only after you run
the Revenue Recognition program.

•Accounting distributions are created only after the Revenue

Recognition program is run.
•For Bill in Advance, the offset account to accounts receivable

is Unearned Revenue.
•For Bill in Arrears, the offset account to accounts receivable i

s Unbilled Receivables.
•Accounting distributions are created for all periods when

Revenue Recognition is run.

Revenue Recognition Program Execution Report :
=======================================
Use the Revenue Recognition Execution report to review all

revenue distributions created for invoices that use invoice and
accounting rules.

This report displays the account class, GL Date, Accounting
Flex field, the currency, amount, and accounted amount for
the revenue distributions Revenue Recognition creates for
each transaction.

Receivables automatically creates the Revenue Recognition
Execution report whenever you run the Revenue Recognition
program, the Revenue Recognition Master program, or the
General Ledger Interfaceprogram.

When the Revenue Recognition program encounters transactions
with problems that prevent the creation of distributions, the
program completes with a status of Warning, and Receivables
includes these transactions at the bottom of this report.

•The Revenue Recognition program gives control over the creation
of accounting entries.
•Submit the Revenue Recognition program manually through the

Run Revenue Recognition window.
•The Revenue Recognition program will also be submitted when

posting to Oracle General Ledger.
•The program processes revenue by transaction, rather than by

accounting period.
•Only new transactions are selected each time the process is run.

Automated Revenue Recolonization Tools in the Market:
-RevPro
-RevStream
-Revenue Edge.