Invoicing Rules

Invoicing and accounting rules let you create invoices that span several accounting periods. 

Accounting rules determine the accounting period or periods in which the revenue distributions for an invoice line are recorded. You can assign a different accounting rule to each invoice line.

Accounting rules of Fixed Duration span a predefined number of periods. Accouning rules of Variable Duration let you define the number of periods during invoice entry.

Invoicing rules determine the accounting period in which the receivable amount is recorded. You can only assign one invoicing rule to an invoice.

Receivables provides the following invoicing rules:

• Bill In Advance: Use this rule to recognize your receivable immediately 

• Bill In Arrears: Use this rule if you want to record the receivable at the end of the revenue recognition schedule.

With Cash Basis Accounting, you only recognize revenue when payment is received. Invoices with rules are therefore not applicable for this method of accounting.

You can assign invoicing and accounting rules to transactions that you import into Receivables using AutoInvoice and to invoices that you create manually in the Transactions window.

AutoInvoicing

AutoInvoice is one of several utilities provided to import transactions. Other options include:

• Oracle EDI Gateway
• Oracle Receivables API's
• XML Invoices (Part of Bill Presentment Architecture)

Despite the availability of alternatives, AutoInvoice is by far the most popular and heavily used integration point for Receivables (AR) transactions.

AutoInvoice is run using the Concurrent Request submission process. Through the Concurrent Request form, AutoInvoice can be scheduled to run on a periodic basis. 

When scheduling or submitting AutoInvoice, parameters allow you to control what data sources are used when importing records and what dates default on transactions.  Additional controls are available on the transaction source that you specify on the records being imported.

AutoInvoice Master Program (RAXMTR):  Upon submission the master program is called. This program coordinates the activities being done such as gathering statistics, marking records for processing (setting request IDs on blocks of records, parallel processing).  The master program also spawns and manages child requests for importing and purging of data.

AutoInvoice Import Program (RAXTRX): The key step in AutoInvoice is the import program.  Upon submission this request is spawned by the Master Program.  It converts the data in the interface table into invoices and also produces the execution and validation reports.

Output of the AutoInvoice Import is referred to as AutoInvoice Execution and Validation report.

AutoInvoice Purge (RAXDEL):  This is conditionally run after import (based upon your AR system options settings).

Tip:

To correct the error, navigate back to the lines form and position your cursor on the Line type field, Click on the folder menu and click on Show field. Doing this will allow you to expose more fields from the table in the form.

Tables involved:

• RA_INTERFACE_LINES_ALL
• RA_INTERFACE_DISTRIBUTIONS_ALL

Oracle Receivables (AR) - Elementary

Oracle Receivables

Trouble Shooting:

Issue: Error 'Please do not supply a GL date when the invoicing rule is Bill in Arrears'.
Sol: Update GL_DATE to NULL if Invoicing_Rule = -3 and Run AutoInvoice.

SEPA

The Single Euro Payments Area (SEPA) is a self-regulatory initiative for the European banking industry championed by the European Commission (EC) and the European Central Bank (ECB). SEPA promises to simplify and harmonize the processes related to cross-border payments in the European community, making it easier for citizens to complete financial transactions with less cost and inefficiencies. 

The aim of the SEPA initiative is to improve the efficiency of cross border payments and the economies of scale by developing common standards, procedures, and infrastructure. The SEPA territory currently consists of 33 European countries -- the 28 EU states, together with Iceland, Liechtenstein, Monaco, Norway and Switzerland.

Part of that infrastructure includes two new SEPA instruments that were introduced in 2008:

• SEPA Credit Transfer (SCT) - a Payables transaction in Oracle EBS
• SEPA Core Direct Debit (SDD) - a Receivables transaction in Oracle EBS

The SEPA Cards Framework (SCF) allows competing banks to create new SCF-compliant debit and credit card 

offerings, within the guidelines laid out by the SEPA authorities. 

Within the Oracle E-Business Suite of applications, Oracle Payables (AP), Oracle Receivables (AR), and Oracle Payments (IBY) provide SEPA transaction capabilities.

Period End Close - Receivables

Period End Close - Receivables

Issue #1: 

Unposted Items Exist :

RA_CUST_TRX_LINE_GL_DIST_ALL

Solution: Run the 'General Ledger Transfer Program' for the org you're trying to close AR period for and try running the AR Close Period program again.

Period End Close - General

Periods represent non-overlapping consecutive date ranges. Every Financials customer needs to successfully close the accounting books each period.
General Steps
Here are some guidelines, from a general perspective, how you can perform the close process for every subledger:
a) Complete transactions
b) Create accounting
c) Reconcile transactions
d) Post to General Ledger
e) Reconcile accounting
f) Close period

Step b), Create Accounting, is a new step in Release 12, as it is an SLA feature. The accounting can be created immediately online, or can be run as a process in the background e.g. as a batch job at a time that matches your business needs.
The important thing to note, is that the accounting is not the distribution on the transaction. The final accounting by SLA could result in different accounting entries being generated based on the accounting rules you have configured. Therefore, you need to ensure that all your accounting for your transactions is created before you post to General Ledger, in order to update the balances correctly.

In Release 11i, when you close your periods in each of the subledgers, Oracle General Ledger will automatically create the balancing lines for journals posted to General Ledger. This changes in Release 12 as subledger accounting creates the balancing lines at the time you account for the subledger transactions.

The subledger accounting journal represents your REAL accounting and the balancing lines are created as part of these subledger accounting journals. When you close a period in Release 12, you’re actually closing subledger accounting. The journals can then be posted to the general ledger to update the GL balances.

Period End Close Dependencies