![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Previous | Next | Contents | Index | Glossary | Library |
Run the programs automatically when periods are opened or closed in the
Control Accounting Periods window
or
Run the programs on an ad hoc basis as part of a report set
Not all accounts have balances stored against them. Only certain control accounts qualify. In Oracle Receivables these control accounts are:
Accounting entries made to Oracle Receivables asset control accounts, such as
Entering Invoices, Debit Memos, Chargebacks, Entering Adjustments, Entering
Receipts, Entering Credit Memos, Entering On Account Credits, and Entering
Discounts
Accounting entries made to Oracle Receivables deposit asset control accounts,
such as Entering Commitments (deposits), Entering Receipts against Commitments
(deposits), and Adjusting/Crediting Commitments (deposits)
Accounting entries made to Oracle Receivables unbilled asset control accounts,
such as Entering Invoices with Bill in Arrears Rules, Entering Receipts
against Bill in Arrears Invoices, Entering Commitments (guarantees) and
Adjusting/Crediting Guarantees
Accounting entries made to Oracle Receivables chargeback control accounts,
such as Entering Chargebacks and Entering Receipts against Chargebacks
Accounting entries made to unapplied/on account receipt accounts, such as
Entering Unapplied Receipts and Entering On Account Receipts. Unidentified receipts
accounts will not have balances stored for them, since there are no
customer/site details.
Accounting entries made to other Receivables accounts pending the transfer of
balances to the cash/bank accounts, such as:
— Confirmation accounts (Entering confirmed receipts/Confirming receipts/Submitting receipts for remittance)
— Remittance accounts (Submitting receipts for remittance/Clearing receipts that have been remitted)
— Bank Charges accounts (Submitting receipts for remittance/Clearing receipts that have been remitted)
The Subledger reports process both posted and unposted transactions (transactions that were successfully transferred to General Ledger, as well as those that were not).
Those transactions that were not posted to Oracle General Ledger should display status information and should indicate whether a transaction is postable. In Oracle Receivables, you can see whether the transaction comes from a complete or an incomplete invoice, or whether it is printed.
All subledger transactions that used any of the above accounts for any accounting purpose are included in the final balance figures. The balances also include unposted transactions that are:
not yet approved
not yet complete
on hold
The reports show all usage of the relevant accounts in the subledger.
The only exceptions are invoices in Oracle Receivables that were defined using invoicing rules and that AutoRule has not yet been run for. You cannot report on these invoices because the accounting distributions do not exist until these invoices are processed by the AutoRule program.
Previous | Next | Contents | Index | Glossary | Library |