ORACLE FINANCIALS E-BUSINESS SUITE, RELEASE 12

PERIOD-END PROCEDURES An Oracle White Paper June, 2009

Oracle Financials E-Business Suite, Release 12 Period End Procedures

i

Introduction
Background
This document has been put together by members of Oracle's internal EMEA Financials Professional Community, acknowledging that every Financials customer needs to successfully close the accounting books each period. Before the first external publication, various people from EMEA Applications Consulting and Financials Product Development have reviewed and enriched the content. Read the paragraph „Status and Feedback‟ below, if you have any comments or feedback.

Objectives
This document provides guidance on period end procedures in Release 12 for Oracle Payables, Oracle Purchasing, Oracle Inventory, Oracle Order Management, Oracle Receivables, Oracle Assets, Oracle Projects, Oracle Cash Management, Oracle Treasury and Oracle General Ledger. It is intended to be generic, and does not relate to a specific organization. Both mandatory and optional steps are included herein. Procedures particular to year-end processing are also described. This document intends to provide a reference for planning period-end procedures for „real-life‟ implementations. It describes the fundamental period-end steps involved for each, with particular emphasis on balancing the subledger applications to Oracle General Ledger, and attempts to provide an overview of the relative timing of these procedures for all installed Oracle applications. It is therefore the intention of this document to provide content from which relevant sections can be extracted, according to the applications installed for a particular organization. Any organization may choose to customize their period-end and year-end processes, for example opting to run additional reports, particular to the organization. Although this document particularly refers to „Period-End Procedures‟, many of the processes can be performed more regularly throughout the accounting period, as required. Each subledger application provides control as to when and how often data is transferred from the subledger application to the General Ledger.

Assumptions
These „Period-End Procedures‟ were written with the assumption that Oracle Financials was implemented for a single operating unit. Where an organization has implemented the „Multi-Org‟ features of Oracle Financials, these procedures would need to be performed for each operating unit individually unless Multi-Org Access Control is enabled. Note: R12 requires multi-org functionality to be used. For further details refer to Oracle® Applications Upgrade Guide: Release 11i to Release 12 Oracle Workflow is incorporated in the Release 12 applications. It is assumed that these Workflow Processes will be monitored and attended to by a System Administrator on a regular basis. Some Workflow Processes like the Requisition Approval Workflow or the Purchase Order Approval Workflow will require a direct response from a message recipient rather than a System Administrator.

Oracle Financials E-Business Suite Release 12 Period End Procedures

Organization
This white paper contains twelve chapters and one appendix where you can find interesting links to more information. The first chapter describes the dependencies between the modules and the biggest change between Release 11i and Release 12, which is the introduction of Subledger Accounting (SLA). Then, the next ten chapters outline period-end procedures appropriate to the Oracle Applications covered in this document. The last chapter displays a summary of the main period-end procedures for each application and the relative timing of each.

Attention: If you are using more than one application, the last chapter is a good reference to see that the order of the steps for each application are undertaken in the right sequence, relative to the other applications you are using.

Status and Feedback
This white paper is intended to be a living document. As we gather new or changed information, we will revise and re-publish this paper. Therefore, we welcome all feedback from you. On the bottom of the My Oracle Support note where you have downloaded this document is a link where you can email us your comments.

Oracle Financials E-Business Suite Release 12 Period End Procedures

Table of Contents
INTRODUCTION ................................................................................................................................................................. II CHAPTER 1 SLA AND PERIOD END CLOSE DEPENDENCIES ................................................................................................... 8 Sub Ledger Accounting (SLA) – Business Process......................................................................................................... 8 Sub Ledger Accounting (SLA) – Process Change .......................................................................................................... 8 Subledger Accounting (SLA) – Reconciliation .............................................................................................................. 9 Subledger Accounting (SLA) Close Process – General Steps....................................................................................... 10 General – Period End Close Dependencies ................................................................................................................ 11 CHAPTER 2 ORACLE ORDER MANAGEMENT ...................................................................................................................... 12 Business Requirements ............................................................................................................................................... 12 Procedures ................................................................................................................................................................. 12 1. Complete All Transactions for the Period Being Closed ...................................................................................... 12 2. Ensure all Interfaces are Completed for the Period (Optional) ............................................................................. 13 3. Review Open Orders and Check the Workflow Status ......................................................................................... 14 4. Review Held Orders ............................................................................................................................................ 14 5. Review Customer Acceptances (Optional) ........................................................................................................... 15 6. Review Discounts ............................................................................................................................................... 15 7. Review Backorders ............................................................................................................................................. 15 8. Review and Correct Order Exceptions ................................................................................................................. 16 9. Reconcile to Oracle Inventory ............................................................................................................................. 16 10. Create Service Contracts (Optional) .................................................................................................................. 16 11. Reconcile to Oracle Receivables (Optional) ....................................................................................................... 16 12. Run Standard Period End Reports ..................................................................................................................... 17 CHAPTER 3 ORACLE CASH MANAGEMENT ........................................................................................................................ 18 Business Requirements ............................................................................................................................................... 18 Procedures ................................................................................................................................................................. 18 1. Complete Daily Cash Management Activities ..................................................................................................... 18 2. Load Bank Statements ........................................................................................................................................ 18 3. Generate Sweep Transactions ............................................................................................................................. 18 4. Create Bank Statement Cashflows....................................................................................................................... 19 5. Reconcile Bank Statements ................................................................................................................................. 19 6. Create Miscellaneous Transactions ..................................................................................................................... 19 6a.Complete Bank Transfers ................................................................................................................................... 20 7. Review Auto-Reconciliation Execution Report .................................................................................................... 20 8. Resolve Exceptions on the Auto-Reconciliation Execution Report ....................................................................... 20 9. Run Bank Statement Detail Report ..................................................................................................................... 20 10. Run Transactions Available for Reconciliation Report ...................................................................................... 20 11. Resolve Un-reconciled Statement Lines............................................................................................................. 20 12. Post to General Ledger ...................................................................................................................................... 21 13. Run the GL Reconciliation Report .................................................................................................................... 21 14. Run the Account Analysis Report for the General Ledger Cash Account ........................................................... 21 15. Review the Account Analysis Report ................................................................................................................. 21 16. Correct any Invalid Entries to the General Ledger Cash Account (Optional) ..................................................... 21 CHAPTER 4 ORACLE PAYABLES ........................................................................................................................................ 22 Business Requirements ............................................................................................................................................... 22 Procedures ................................................................................................................................................................. 22 1. Complete All Transactions for the Period Being Closed ...................................................................................... 22 2. Run the Payables Approval Process for All Invoices ............................................................................................ 23 3. Review and Resolve Amounts to Post to the General Ledger ............................................................................... 23 4. Reconcile Payments to Bank Statement Activity for the Period............................................................................ 24 5. Transfer All Approved Invoices and Payments to the General Ledger ................................................................. 24 6. Review the Payables to General Ledger Posting process After Completion. ......................................................... 25 7. Submit the Unaccounted Transactions Sweep Program ....................................................................................... 25 8. Close the Current Oracle Payables Period ........................................................................................................... 26
Oracle Financials E-Business Suite Release 12 Period End Procedures

................... 40 3.................................................... 32 Project Periods and General Ledger Periods .......... 45 11..... 39 21............................................ Open the Next Oracle Receivables Period.................... 34 5............................................................ 43 5............................................................................................................................................Check With Suppliers ........................................................... 37 11........................................................................................................................ 46 16........... Review Account Analysis Report ....................................................................................................................................................................................................................... Complete All Transactions for the Period Being Closed ............................................................... Run Final Project Costing and Revenue Management Reports...................................................... 48 3............................................................................. Generate Draft Revenue for All Projects...................................................................................................................................................................... 46 14... 42 4.............................................................................................................................................................. Open the Next Oracle Projects Period ............................................................. Run the Cost Distribution Processes ................ 47 18........................................................... 37 10.................................................................................................. 32 Business Requirements ..... Complete All Transactions for the Period Being Closed ................................................................................... Advance the PA Reporting Period (Optional) ........................................................................................................ 33 Procedures ..................................... Permanently Close the Oracle Projects Period (Optional) ......................................................................... 33 2........... Reconcile Outstanding Customer Balances ................ Complete All Transactions for the Period Being Closed ...................................................................................... 40 Business Requirements .................... 32 Period Statuses .......................................................................................... 38 16... Run the Generate Cost Accounting Events Program ................................. Run the Key Indicators Report (Optional) ........................................ Reconcile Transaction Activity for the Period ..... 39 20........................................................ Run Create Accounting to Process Revenue Accounting Events ...................................................................................................... Generate Invoices ........................... 39 CHAPTER 6 ORACLE RECEIVABLES . Third Party Balances Report ..................................................................................................................................... 49 4.......................................................................... 45 10.................................................................. Interface Cost Transactions to Other Applications .... Change the Current Oracle Projects Period Status from Open to Pending Close ............................. 43 6......................... 32 General Exception Handling at Period End ........ 29 12. 38 15............................................................................................................................................................................................................... 35 6a........................................ Review the Current and Future Commitments (Optional) ......................... 26 10................................................................................ 37 13............................................................................. 46 15.......... Run Maintenance Processes ..................................................................................... 30 CHAPTER 5 ORACLE PROJECTS ... Review the Subledger Period Close Exceptions Report ........................................................................ Close the Current Oracle Receivables Period ................................................................. 33 3.... Update Project Summary Amounts ...................................................................................................................... 33 1....................................... 37 12........................... Reconcile Posted Journal Entries ......................................................................................................................... 45 12............................................................................................. 44 7......................................... Run Generation Revenue Accounting Events Process ......................................................................................................................................................................... 34 6.................................................................................................................... Review the Unposted Items Report ........ Post to the General Ledger ................................................................................................................. Run Mass Additions Transfer to Oracle Assets.............................. Accrue Uninvoiced Receipts ........................... 26 11....................................... Reconcile Receipts to Bank Statement Activity for the Period ............ 48 Business Requirements ............................................... Complete all Maintenance Activities ....................... Restore Access to User Maintenance Activities .............9....................................................................................................................................................................... Run Period Close Exceptions and Tieback Reports . 39 18............................................................................. 40 1............................................................... Run Reports for Tax Reporting Purposes (Optional) ....................... Run Reports for Tax Reporting Purposes (Optional) ..... Reconcile Receipts ............................................................................................................................... Reconcile Oracle Payables Activity for the Period .. 47 CHAPTER 7 ORACLE PURCHASING .................................................................... 36 7............................... 40 Procedures .......... Reconcile the Journal Import Process ............................ Transfer Invoices to Oracle Receivables ....................................................................................................................................................... Review the Outstanding and Overdue Purchase Orders (Optional) ...................................... 48 Procedures ......................................... 39 19................ 44 8...................................... 36 8.......................... 29 13....................................... Review the Unapplied Receipts Register ............................................. 40 2............................................................................................................ Follow Up Receipts .......... Reconcile Cost Distribution Lines with General Ledger (Optional) ................................................................................................................... 46 13........................ 48 1............................................................. 49 Oracle Financials E-Business Suite Release 12 Period End Procedures ............................. 37 14....................................................... 33 4......................... 44 9..................................................................................................................................................................................... 29 14................................................................................................................................ Change the Current Oracle Projects Period Status from Pending Close to Closed ................ Review and Release Revenue for All Projects ..................................................................................................................................... 46 17................................................ Print Invoices.................................................. Reconcile the General Ledger Transfer Process ..................................................................... Open the Next Oracle Payables Period .. 36 9.................................................................................................................................... 48 2.............................................................................................. 38 17.........................................................................................................................................

............................. Rollback Depreciation ...................................................................................................................................... Close the current Oracle Payables and Oracle Purchasing Periods .......................................................... Run Standard Period End Reports (Optional) ................................. 64 6....................................................................... 63 1....................................................................................................... Complete All Transactions for the Period Being Closed .................................................. Run Depreciation ....................... 63 Business Requirements .......................................................... Transfer Summary or Detail Transactions .............................................. Reconcile Accrual Accounts ...............................5.................. 53 11...................... Check Inventory and Work in Process Transaction Interfaces ................. 63 3................ 49 7............................. Reconcile Oracle Assets to the General Ledger Using Reports........................................................................................................................................................................................................................ 74 Oracle Financials E-Business Suite Release 12 Period End Procedures ....................................................................................... 68 4........................................................................................................................................... 72 6................... Post All Journal Batches ................ Ensure the Next Accounting Period Status is set to Future Entry ............................................. Create Deferred Depreciation Journal Entries (Optional) ....... 68 3..... Perform Year End Encumbrance Processing (Optional) ............ 68 Procedures ............ Run Responsibility Reports (Optional) ............................................................... 74 11.................................. Close the Current Oracle Purchasing Period...................... 59 3............. 60 7.......................................................................................................................................................................................................................................................................................................................................................... 65 7................................................... 67 CHAPTER 10 ORACLE TREASURY..........................................................................................Perpetual Accruals ........................................................................................................................................... Check and fix pending Transactions ..Period End Process ........................................................................................................................................................ 55 CHAPTER 8 ORACLE INVENTORY-COST MANAGEMENT ............................ 72 9.... 72 5.......................................................................... Complete Daily Trading Activities ................................................... 61 9..................... Complete the Oracle Payables Period-End Process ......... 63 Procedures .................................................................................................................................................................................................................................................. Run GL Trial Balances and Preliminary Financial Statement Generator Reports (FSGs) .......................... 70 Business Requirements ....................................................................................................................................................................................... Run the Receipt Accruals ............ Depreciation Projections (Optional) .................... 71 3........................................... Generate Reversal Journals (Optional) ..................................................... 65 9................................................................................ Transfer Journals to General Ledger ...................... Complete Non-Oracle Sub-ledger Interfaces to Oracle General Ledger (Optional: only required if you want to post from non-Oracle systems) ............................ 58 Procedures ........................................................................................... 74 12................ 55 12......................................................................... 62 CHAPTER 9 ORACLE ASSETS ........................................................................................................ Open the Next Inventory Period ........................................................................................................... Perform Revaluation ...................... Run Standard Period-End Reports and reconcile the Perpetual Inventory with GL ........................................................................ 71 1............... 72 7................................................... 50 9................................................................................... 69 CHAPTER 11 ORACLE GENERAL LEDGER .................................................................................................................................... 69 5... 58 1.................................... 60 6........................................................... Close the Current Inventory Period .............................................................................................................................. 66 11...................... 71 2............................................................................. Run the Period Close Exceptions Report .............................................. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger .............. Assign All Assets to Distribution Lines ........................................................................................................................................... 58 Business Requirements ...................................................................................................................................................................... Translate Balances (Optional) ......................................................................................................................... 70 Procedures ...................................... 72 8.................................................... 74 10................................................................................................................. Validate the Work in Process Inventory .......... 68 Business Requirements ..................... Generate Mass Allocation Journals (Optional) ................................................... 59 5..................................... 66 10.............................................. 50 10........... 49 6............................ 59 4............ 64 5.............................................................................. 49 8..... 63 4..................... 68 1.......................... Follow Up on Outstanding Invoices ................ 58 2.................................................................... Generate Journals .......................................... 70 Combined Basis Accounting ........................................................ Revalue Balances (Optional) ................................................... Create Accounting ..................................... Run Calculate Gains and Losses (Optional) ........ 63 2.................................................. 73 9a...................................................................................................................................... 70 Period End Close ........ 72 4.............. Open the Next Oracle Purchasing Period ................................................................................................ 68 2.................................................... Complete All Transactions for the Period Being Closed ......................... 65 8.................................................... Upload Journals from Web Applications Desktop Integrator (Web ADI) to Oracle General Ledger (Optional) ......................... 55 13............................. Review and Post Journal Entries ................................................. Generate Accruals and Amortization ..................................................................... Identify and Review Un-invoiced Receipts (Period-End Accruals) ............ 60 8................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. Generate Recurring Journals (Optional) ................................................................................................................................... Review and Verify Journal Details of Unposted Journal Entries .......................................................................

........... Perform Final Adjustments ......................................SUMMARY .............................. Run Financial Reports for the Closed Period ........................................ 75 13a....................... 81 APPENDIX: MORE INFORMATION ................. 77 16............................................................................ Enter Adjustments and / or Accruals and Post ....................................................................... Run Reports for Tax Reporting Purposes (Optional) ..................................................................................................................................................................................................................... 76 15..................... 78 19......................... Open the Next Oracle General Ledger Period ............................................................................................................................................................. Consolidate Ledgers (Optional) ....................................................... 79 CHAPTER 12 PERIOD END PROCESSING ......................................................................................................... 87 Related My Oracle Support Information ........................ 87 CHANGE LOG ........ Reconcile Intercompany (optional) ........................................ 78 18................................................................................................................................... Review and Correct Balances (Perform Reconciliations) .......................................................... 88 Oracle Financials E-Business Suite Release 12 Period End Procedures ......................................................................................................................................13......................................................................................................................... 78 21................................................................................ Perform Encumbrance Year End Procedures (Optional) .... 76 14...................... Close the Current Oracle General Ledger Period ............... 78 20................. 77 17.........

and for ease of drilldown. Subledger Accounting provides a comprehensive view of all subledger accounting data. the accounting is generated by Subledger Accounting. Oracle Financials Release 12 Period End Procedures 8 . so that you can maintain a simple chart of accounts and store only what is needed for GL reporting and analysis. Subledger Accounting helps to maintain a common link between General Ledger (GL) balances and underlying transactions automatically. It behaves like a detailed version of your general ledger and provides a rich store of information for reporting and analysis. Whenever you want to account for your subledger transactions. • Just as Oracle General Ledger stores balances and journals. Sub Ledger Accounting (SLA) – Process Change Due to the impact of the Subledger Accounting Architecture the close process has changed between Release 11i and Release 12. for internal and external audit purposes. online or as a background batch process. • It allows your general ledger to be free of extraneous data. Subledger Accounting offers a new model between the subledgers and GL. you can go directly to Subledger Accounting to see the detail from all transaction sources that feed the GL account balance without having to go back to multiple source systems and applications. Subledger Accounting stores subledger balances and subledger journals for all of your subledgers that require accounting.Chapter 1 SLA and Period End Close dependencies Sub Ledger Accounting (SLA) – Business Process The new Subledger Accounting architecture in Release 12 provides a common repository of all your accounting information. • The moment you need to access more detailed information.

Therefore.In Release 11i the transactions and distributions represented the accounting. Oracle Financials E-Business Suite Release 12 Period End Procedures 9 . You can still reconcile transaction reports to accounting reports. This changes in Release 12 as subledger accounting creates the balancing lines at the time you account for the subledger transactions. The journals can then be posted to the general ledger to update the GL balances. especially if you have altered your subledger accounting rules. In Release 11i. The subledger accounting journal represents your REAL accounting and the balancing lines are created as part of these subledger accounting journals. you‟re actually closing subledger accounting. Oracle General Ledger will automatically create the balancing lines for journals posted to General Ledger. customers and transactions. distributions on transactions in subledgers are considered to be the default accounting and should therefore not be used for reconciliation purposes. the subledger accounting becomes the single source of truth for accounting reconciliations. When you close a period in Release 12. the balances are displayed but not the transactional information. In Release 12. there is no reason to reconcile distributions on transactions to the general ledger. you reconciled transactions and distributions to the general ledger through transactional reports. The point to note is that when you do account balance reconciliation. The reason is that subledger accounting enables you to change the accounting for transactions so it is different from the default accounting. you should ignore distributions in Release 12. In Release 12 however. when you close your periods in each of the subledgers. The new accounting reports in Release 12 now also contain more comprehensive information .not just on balances but also on suppliers. Differences between R11i and R12 Subledger Accounting (SLA) – Reconciliation From a reconciliation perspective the picture below shows what has been changed between R11i and R12. In the accounting reports in Release 11i. In Release 11i.

The accounting can be created immediately online. The important thing to note. as a batch job at a time that matches your business needs. you need to ensure that all your accounting for your transactions is created before you post to General Ledger. 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. Oracle Financials E-Business Suite Release 12 Period End Procedures 10 . is that the accounting is not the distribution on the transaction. or can be run as a process in the background e. The final accounting by SLA could result in different accounting entries being generated based on the accounting rules you have configured. Therefore.Reconciliation between R11i and R12 Subledger Accounting (SLA) Close Process – General Steps Here are some guidelines. in order to update the balances correctly. is a new step in Release 12. from a general perspective. as it is an SLA feature.g.

you have to close Oracle Payables before you close Oracle Purchasing to account for purchasing accruals at period end. Finally. you close all of your subledgers before you close General Ledger.General – Period End Close Dependencies Before you start with the Period-End process you have to know what the dependencies are between the various modules as described in this document. as bank reconciliation in Cash Management will create miscellaneous receipts in Oracle Receivables and so forth. Oracle Financials E-Business Suite Release 12 Period End Procedures 11 . You actually have to close Oracle Cash Management before you close Oracle Receivables. The diagram above shows the dependencies between some of the main Financials products and a couple of supply chain products. You also need to close Oracle Payables before you close Oracle Inventory and Oracle Assets. For example.

Implicit Acceptance Confirm shipments and optionally. windows and report queries retrieve open orders only. since many programs. * Close lines and close orders are implemented using workflow.Chapter 2 Oracle Order Management This chapter describes the procedures for performing period-end processing in Oracle Order Management Release 12. so reporting can be limited only to the active orders. respectively. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed Enter and book all orders Schedule orders Enter and book return material authorizations Run the Generate Pre-billing Acceptance Program for Pre-billing. Order Management provides seeded close line and close order workflow sub-processes to close the order header and line. the creation of install base entries for shipments Confirm OM-shipping transaction for the period Sales order acknowledgments Cancel backordered included items Respond to workflow approval notifications Confirm that invoice interface (OM-> AR interface) has been completed Optionally. when included in the order header or Oracle Financials E-Business Suite Release 12 Period End Procedures 12 . increasing system speed and efficiency. Procedures The following steps are taken in performing period-end processing for Oracle Order Management. confirm that service contracts for warranties and extended warranties have been created Close orders * Closing orders that are complete enhances performance. appropriate actions should be undertaken to finalize the Order Workflows and close these Sales Orders. 1. These processes. Business Requirements Open Sales Orders should be reviewed and. Closed orders are excluded from many of the standard reports available in Order Management. Orders marked as closed are not selected. where possible.

Ensure all Interfaces are Completed for the Period (Optional) Ensure that all interfaces for the current period have been processed: Order Import from External Order Systems.If orders or lines have activity specific holds present. * If you are using external order processing systems for data entry of orders. Oracle Financials E-Business Suite Release 12 Period End Procedures 13 . perform the above tasks for each operating unit. ensure that the processes calling the public API have completed. the following processes need to be completed: a) Enter and approve all internal purchase requisitions in Oracle Purchasing. for which you can define processing constraints. if you are using the Order Management public API to create orders. use the Order Import to update Oracle Order Management from your external systems. Order Import from Oracle Purchasing for Internal Orders. Order lines can close independent of each other. b) Run the Create Internal Sales Orders Process in Oracle Purchasing for all requisitions within the current period. 2. * Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process. they will not be closed by workflow activity. no lines can be added or changed. Once an order line is closed. Close Order Lines * An order line is eligible to close when it completes all of the line-level activities within the workflow process. * The order header close order process checks at the end of every month to see if all the lines associated with it are closed. no changes can be made to any fields except the descriptive flexfield. Attention: Be sure to include the standard sub-processes of close line and close order at the end of all your line and order flows to ensure that your orders and returns close once all prerequisites have been met. If you are using Oracle Purchasing to process Internal Purchase Requisitions.line workflow. close the status of the eligible order or lines. Alternatively. It closes the order header if it finds that all the lines are closed. Holds Effect on Eligible Lines * The close order and close line workflow activities will close order or lines if only generic holds are present . Attention: If MOAC is enabled for the Order Management responsibility. Use the Error Message window to determine if your data failed to import. Once an order is closed.

for external orders. f) Invoice Interface / AutoInvoice. items. From the status page. The Workflow Status option on the Sales Orders window Tools menu launches the Workflow Status page. order numbers. Use the Error Message window to determine if your data failed to import. d) Run the Internal Order and Purchasing Requisition Discrepancy Report which displays the differences between the purchasing requisition entered and the actual items ordered during order entry. 4. requisition numbers. scheduled dates. ship to information. The window shows in tabular format all the activities an order header or line has completed and the corresponding results. The order line status is displayed in the main tab of the Line Items tabbed region. The Sales Orders window displays the order header status in the main tab of the Order Information tabbed region. you can access the Workflow monitor to see the order or line status in a more graphical format. inventory-sourced requisition lines to the Order Management interface tables. Then. Review Held Orders Run the following reports to assist with reviewing sales orders on hold: Oracle Financials E-Business Suite Release 12 Period End Procedures 14 . Review Open Orders and Check the Workflow Status Use the Sales Orders Workbench to review open orders using the Advanced Tabbed Region to specify controls such as whether to find closed orders/lines and cancelled orders/lines. order types. This process will ensure all shipped sales order information is transferred to Oracle Receivables when it reaches the appropriate point in the order workflow. e) Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process. This is available through the View Diagram button. order date ranges. as well as credit memos and credits on account created from returns. Internal orders do not go through the Invoice interface/ AutoInvoice process. c) Run Order Import to create internal sales orders from internal requisitions. Attention: This process is only applicable for Order Workflow Definitions that include the Invoice Interface or Invoice Line processes. Attention: Order Management does not process internal sales order lines for the Invoice Interface. This report includes all open and closed orders. The Create Internal Sales Orders and Order Import processes can be scheduled to run automatically at specified intervals. 3. even if the Invoice Interface is an action in the order Workflow Definitions for the Internal Sales Order transaction type.Use the Create Internal Sales Orders process to send requisition information from approved. The AutoInvoice Process updates Oracle Receivables for invoice and revenue information. the Order Import process is run from within Order Management to generate the internal sales orders. and internal requisition and internal sales order hold discrepancies.

and exceptions are clearly identified and reviewed and/or followed up. Review Backorders Review backlogs and backorders to ensure that these items are current. or identifies why a particular order is on hold. process cancellations for items/lines which are no longer required. order date. including agreement. c) Outstanding Holds Report The Outstanding Holds Report reviews order holds for the customer or customers you choose. If necessary. including the factor for shipments and receivables for a certain number of days. salesperson and total order discount. This report indicates the date and the type of activity for each hold transaction. This report provides detailed line pricing information. selling price. the revenue recognition process is deferred and linked to customers accepting the shipped goods. ordered items. and order number. once the goods are accepted. b) Hold Source Activity Report The Hold Source Activity Report reviews holds placed and removed under a hold source during the time period you specify. 7. This report provides order level pricing information. It is automatically sorted by customer. Use the following reports: a) Order Discount Detail Report The Order Discount Detail Report reviews discounts applied to orders by order line detail. order line. and order amount for each order line on hold for each customer you select. All balances are calculated as they are using the online credit check rule. order number. and then order line detail. This report displays the order number. credit check rule. Review Customer Acceptances (Optional) In Pre-Billing Customer Acceptance. Review Discounts It is recommended that you review discounts processed as part of the order process to ensure appropriate discount policies have been followed. 5. order number. 6. Order Management allows you to perform a credit check on customer orders and automatically places orders on hold that violate your credit checking rules. including price list price. and discount information. currency code. b) Order Discount Summary Report The Order Discount Summary Report reviews discounts applied to orders. a) Backorder Detail Report The Backorder Detail Report reviews all customer orders that have been backordered. In Post-Billing Acceptance. invoicing is carried out. This report provides details for each order including customer name.a) Orders on Credit Check Hold Report The Orders on Credit Check Hold Report identifies all of the credit holds currently outstanding for a customer within a date range. This report is automatically sorted by customer. Oracle Financials E-Business Suite Release 12 Period End Procedures 15 .

total quantity both ordered and backordered. When Exception Management encounters this situation. Order Management automatically sorts this report by currency. Review and Correct Order Exceptions The following reports should be reviewed. which needs to be corrected. customer name and number. b) Retry Activities in Error There are cases when retrying a workflow activity in error will not resolve the problem. Reconcile to Oracle Inventory Run the following reports for reconciliation with Oracle Inventory: a) Backorder Detail Report b) Review Backorders (Already discussed under section 7. Reconcile to Oracle Receivables (Optional) Run the following reports to assist in reconciliation of orders invoiced in the period: Oracle Financials E-Business Suite Release 12 Period End Procedures 16 . It displays order information such as order number. b) Backorder Summary Report The Backorder Summary Report lists all unshipped orders. They may indicate incomplete processing. 11. return reason. This report also includes total amounts for customers and currencies. last shipped date. and then item.) c) Returns by Reason Report The Returns by Reason Report reviews all return material authorizations for various return reasons. 10. c) Sales Order Workflow Status Report The Sales Order Workflow Status Report enables Order Management users to locate orders that are not progressing through associated workflows as expected. and the monetary amounts ordered. These amounts involve totals for shippable items only. purchase order. This report includes only open orders in an order cycle that includes pick release. or deleted as appropriate. 9. shipped and outstanding. and exceptions corrected before completing the Order Management/Receivables period end: a) Unbooked Orders Report Use this report to review orders entered but not booked. completed. order date. and monetary amounts of both ordered and backordered quantities. all backordered items and their appropriate line numbers. 8. the workflow activity is set to „notified‟ instead of being retried. order type.order type of each order. Create Service Contracts (Optional) Run the Service Contracts Order Processing Concurrent request to create service contracts for extended warranties.

A variety of parameters can be used to print the invoice information for a specific order or group of orders. Implicit Acceptance. agreements. and who cancelled the order. including order number. The report displays all open and closed orders for a salesperson. Salespeople can use this report to see their current outstanding orders and their status. If there are no invoices for a particular order that meets the parameter criteria. This report provides a summary of each cancelled order. shipped. the quantity ordered and the quantity cancelled. c) Customer Acceptance Report Generate Pre-billing Acceptance Program for Pre-billing. order date ranges. customer name. the date and reason the order or order line was cancelled. If only a delivery name is specified when defining the parameters of this report. Run Standard Period End Reports The following reports should be run each period: a) Cancelled Orders Report The Cancelled Orders Report reviews all orders that have been cancelled. b) Salesperson Order Summary Report The Salesperson Order Summary Report reviews orders for one or more salespeople. and invoiced and their potential commission. review cancellations by salesperson. and allows evaluation of the most common cancellation reasons. order numbers. quantity ordered. cancelled. Shipping Execution prints one commercial invoice per delivery within the trip. This report shows open orders. or review cancellations by customers. Order Management prints in the report that no invoices exist for that order. order types. This report displays the order and each order line associated with each salesperson.a) Commercial Invoice (for all ship dates within the current AR period) The Commercial Invoice Report lists all confirmed shipped items in a delivery. Oracle Financials E-Business Suite Release 12 Period End Procedures 17 . and detailed sales credit information for lines in a selected range. customer or customer number. line type. b) Order/Invoice Detail Report The Order/Invoice Detail Report reviews detailed invoice information for orders that have invoiced. This report can be used to report total amounts cancelled in a specified time-frame. line number and item. 12.

Once the bank statements are imported. create sweep Oracle Financials E-Business Suite Release 12 Period End Procedures 18 . including bank account information. It provides comprehensive bank reconciliation. Bank statements can be either manually entered or loaded electronically from information received directly from your bank. Business Requirements Oracle Cash Management is an enterprise cash management solution that helps you effectively manage and control the cash cycle. The program will scan the bank statement for sweep lines and. bank branches & internal bank accounts setup. based on the cash pool setup in the system. Refer to “Entering Bank Statements Manually” and “Loading Bank Statement Open Interface” in the Oracle Cash Management User Guide. such as bank charges and interest. you can automatically generate system transactions to match banking information once the bank posts the sweeps. 2. run the Sweep Transaction Generation concurrent program. Load Bank Statements Detailed information from each bank statement. The Bank Reconciliation process enables the verification of entries on the Bank Statement by reconciling that information with system transactions in Oracle Payables. validate them. Oracle Receivables and Oracle General Ledger. Cash forecasting is a planning tool that helps anticipate the flow of cash in and out of the enterprise. and checks cleared needs to be entered into Cash Management. For organizations with high transaction volumes bank statements should be loaded and reconciled on a daily basis. and send payment instructions to the bank. Generate Sweep Transactions If you have target balance or zero balance accounts (ZBA) with your banks. During the Bank Reconciliation process miscellaneous transactions can be created for bank-originated entries.Chapter 3 Oracle Cash Management This chapter describes the procedures for performing period-end processing in Oracle Cash Management Release 12. 3. Complete Daily Cash Management Activities Complete bank account transfers for the day. cash pooling and flexible cash forecasting. if necessary. allowing the projection of cash needs and evaluation of the company's liquidity position. 1. bank. intra-bank account transfers. deposits received by the bank. Procedures The following steps are taken in performing period-end processing for Oracle Cash Management.

the information must be reconciled with the subledger transactions. you will need to re-run the „Create Accounting‟ routine from Oracle Receivables to ensure all information is transferred to the General Ledger. Reconcile Bank Statements Once detailed bank statement information has been entered into Cash Management. 4. and create cashflows. run the Bank Statement Creation concurrent program. Create Bank Statement Cashflows If you have recurring items such as bank fees and interest appear on your bank statement. Oracle Payables payments or Oracle Receivables receipts can also be manually created. Cash Management provides two methods to undertake reconciliations: a) Automatic Bank statement details are automatically matched and reconciled with subledger transactions. This method is ideally suited for bank accounts which have a high volume of transactions. This method is ideally suited to reconciling bank accounts which have a small volume of monthly transactions. which can be accounted for and subsequently reconciled. such as bank charges and errors can be created.transactions between your internal bank accounts. Attention: If you create transactions during the reconciliation process. This program will scan the bank statement for specific codes. Note: The automatic reconciliation process can be set up to create miscellaneous transactions automatically. The manual reconciliation method can also be used to reconcile any bank statement details. 6. b) Manual This method requires a manual match of bank statement details with subledger transactions. Create Miscellaneous Transactions During the reconciliation process. Refer to “Reconciling Bank Statements Manually” in the Oracle Cash Management User Guide. Oracle Financials E-Business Suite Release 12 Period End Procedures 19 . 5. miscellaneous transactions for bank-originated entries. as defined in the Bank Statement Cashflow Mapping. which could not be reconciled automatically. you can use the Bank Statement Cashflow Creation program to create system transactions (cash flows) to match banking information. Once the bank statements are imported. Refer to “Reconciling Bank Statements Automatically” in the Oracle Cash Management User Guide. which can be accounted for and subsequently reconciled.

Review Auto-Reconciliation Execution Report Once the reconciliation process has been completed. and Amount. 10. This report groups transactions by status so that void or reversed transactions are separate from other transactions. Detailed information includes the Customer. and the statement totals for each type of transaction. 11. and reconciled transaction detail. 9.Complete Bank Transfers Complete the bank account transfer whether it is manual or automatic and record the validation if required before completing the transfer. This report shows import and reconciliation errors that occurred when running the Auto-Reconciliation program. Run Bank Statement Detail Report This report shows statement and transaction information for a specific bank account statement. It lists detailed transaction information for your Available Receipts. statement line detail. This report includes either statement import errors. 7. over-reconciled and under-reconciled.6a. You may also request it as needed from the Submit Request window. Run Transactions Available for Reconciliation Report This report shows all transactions available for reconciliation for a specific bank account. and gives you the option to select only un-reconciled statement lines. which prevented the automatic loading of your bank statement. Transaction Number. Resolve Exceptions on the Auto-Reconciliation Execution Report Resolve the exceptions on the Auto-Reconciliation Execution report by either rerunning the import process or by manually reconciling the exceptions. This report lists the details of any miscellaneous transactions that were created in Receivables during the automatic reconciliation process. Transaction Date. Supplier or Batch Name. This report lists any un-reconciled transactions separately with their current status. reviewing the reconciliation results is recommended. or your reconciliation exceptions found during the automatic reconciliation process. This report only lists void payments if the Show Void Payments option on the Systems Parameters window is checked. including bank statement header information. Payment Method. Resolve Un-reconciled Statement Lines Resolve the un-reconciled statement lines by manually reconciling the statement lines to the available transactions. Available Payment. reconciled. and Available Journal Entries for reconciliation. It does not list reversed receipts due to user error nor does it list the associated original receipts that were not reconciled. 8. un-reconciled. Currency. including the amount entered. Cash Management automatically produces this report during the automatic reconciliation process. Oracle Financials E-Business Suite Release 12 Period End Procedures 20 .

14. Please make sure you are satisfied with the draft journal entries before creating final accounting. you can later submit the "Transfer Journal Entries to GL" concurrent program. 13. 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. Valid sources will include Payables and Receivables. The program creates and optionally transfers and posts journal entries to General Ledger. Such journals cannot be transferred or posted to General Ledger. 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. in which case draft journal entries will be created. Warning: To ensure that this report is accurate. and journal entries. If you do not transfer the journals to General Ledger immediately. Attention: Final journal entries cannot be further modified in Cash Management. * Transfer journal entry transactions from Oracle Payables and Oracle Receivables to your General Ledger. if transfer from sub-ledgers was not in FINAL POST mode. Transactions entered directly via General Ledger will have a Source of Manual or possibly Spreadsheet if Web Applications Desktop Integrator (Web ADI) is used. Post to General Ledger Create journal entries for eligible accounting events generated by Bank Account Transfers and Bank Statement Cash Flows by submitting "Create Accounting" concurrent program. It also lists a separate adjustment amount for un-reconciled receipts. 15. * Post journals in General Ledger. In addition to creating final accounting entries. To prevent invalid journal entries to the General Ledger Cash Account enable security rules appropriately. 16. This report lists a balance and an adjusted balance for the bank statement. the program can be run in a draft mode. you must first perform these tasks: * Reconcile all statements in Cash Management. 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. Run the GL Reconciliation Report Use this report to reconcile the General Ledger cash account to a bank statement balance. payments.12. Oracle Financials E-Business Suite Release 12 Period End Procedures 21 . as well as bank errors.

All of the operating units that share a ledger also share the same period statuses. Subledger Accounting online inquiry and BI Publisher reports can be utilized to report and analyze balances. When you update the period status to „open‟ in one operating unit. The posting level for Oracle Payables must be determined when planning period-end procedures. Business Requirements Accounts payable activity must be reconciled for the accounting period that is to be closed. Where detail level accounting transactions are required to be posted to the General Ledger using sub-ledger accounting (hereafter referred to as SLA). 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. and posting and report processing speed degradation caused by the sheer volume of posted transactions. the system asks you to resolve the un-posted transactions for those operating units before it allows you to Oracle Financials E-Business Suite Release 12 Period End Procedures 22 . Completing all transactions for Oracle Payables: * Complete Invoices and Credits * Complete Prepayments * Complete Expense Reports * Complete Invoice Import * Complete Payments If you import transactions from an external system. When you attempt to update the period status to „closed‟ in one operating unit.Chapter 4 Oracle Payables This chapter describes the procedures for performing period-end processing in Oracle Payables Release 12. there may be technical constraints involved. the system checks for unposted transactions in all operating units within the ledger. and reviewed all audit trails for completeness. In Release 12 the detailed level of posting can be controlled by GL summarize options and also at SLA journal line type level. Subledger Accounting can contain all of the detailed subledger accounting level analysis. Then. so that the general ledger can remain “thin”. ensure you have imported all transactions. If there are unposted transactions in any of the operating units. Procedures 1. and their transactions. that period is opened for all operating units within the ledger. The following steps are taken in performing period-end processing for Oracle Payables. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed. or you are using Internet Expenses or Xpense Xpress. relating to the physical data storage volume.

3. The report details all invoices that Oracle Payables cannot select for posting and therefore cannot create journal entries. and those which have not been posted but have been accounted. and voucher number. event type. supplier name. Note that this report does not include invoices that have no distributions. resolve any identified holds which will prevent posting to the general ledger. and then re-run the Payables Approval process to approve these invoices. 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. When a transaction is accounted with errors. Where possible. b) Review the Journal Entries Report This report enables review and analysis of accounting entries in the Payables subledger. exception. d) Optionally run a Payment Process Request at the month end By running a month end Payment Process request. You can then correct the problems and resubmit the accounting process. c) Review the Unaccounted Transactions Report This report enables review of all unaccounted invoice and payment transactions and a view of the reason that Payables cannot account for a transaction.close the period for the ledger. The report also lists. Oracle Financials E-Business Suite Release 12 Period End Procedures 23 . This report is owned by SLA. If Multi-org Access Control is implemented. and event class. document number. in detail. category. By altering the parameters. transactions that have been accounted with error and all entries that could not be transferred to the general ledger. you can produce a detailed or summary listing of the accounting information you want to review. so that they can be paid by Oracle Payments and posted to the general ledger. you may create a payment for as many due invoices as possible. period closing can be performed across OU‟s from a single responsibility. supplier. review the details and make necessary changes. source. Run the Payables Approval Process for All Invoices Run the Payables Approval process to approve all unapproved invoices and invoice lines in the system. 2. transaction currency. Accounts Payable sorts the report by transaction type (invoice or payment). ledger currency. through one OU at a time. and transaction number. the report also lists those transactions which have been posted in the general ledger. Using the report parameters. SLA groups the report by ledger. Run this report after you have run the Create Accounting Process. Data is then sorted by accounting date. The report will then show only transactions that had problems that prevented accounting. as accounted by SLA.

This report is automatically submitted when payment instructions are being created and can also be submitted from the standard report submission (SRS) screen. Check the status of the Payment Process Request/Payments/Payment Instructions to ensure that all payments have been processed. make sure there are no errors reported on this report. Oracle Financials E-Business Suite Release 12 Period End Procedures 24 . f) Optionally run the Payments Register The Payment Register details payments printed in a particular accounting period. Attention: Oracle Payables prevents the closing of a period in which all payments have not been confirmed. The transactions that have been accounted in Final Post have already been transferred to. This report can be used to review payment activity for each bank account used during the specified time period. whereas the Posted Payment Register total is the total payment amount. The transactions in draft accounting mode can be included on accounting reports but cannot be transferred to the general ledger. including setup and overflow payment documents. When accounting mode is Final and transfer to GL is set to „No‟ then. The Payment Instruction Register lists each payment created for a payment process profile or for a manual payment. The report lists each payment in a payment process request. The journal entries are posted in Oracle General Ledger to update account balances. If only verifying report totals. Transfer All Approved Invoices and Payments to the General Ledger Release 12 provides 3 modes of accounting: Final. Use Oracle Payments to confirm any payment instructions. Reconcile Payments to Bank Statement Activity for the Period Refer to Chapter 3 Period-End Procedures for Oracle Cash Management. and posted in the general ledger. Final Post and Draft. Actual payments can be compared against this register to verify that Oracle Payables/Oracle Payments has recorded payments correctly. by payment number. 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. Warning: The report total only shows the net (less discounts) payment amount. 5. including discounts. “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.e) Confirm all Payment Instructions Run the Payment Instruction Register for the period that is to be closed. A draft entry does not update balances and does not reserve funds. these two reports would not balance. in ascending order. or finalize any outstanding payments. SLA creates detail or summary journal entries for all eligible events when you post. 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.

For example. Review the Payables to General Ledger Posting process After Completion. 7. if your accounting practices permit it. you might want to use this program to change the accounting date of the transactions to the next open period. and credit the liability account specified on the invoice.e. Posting is determined by the parameter „Post in GL‟ which is set during Create Accounting.Invoice journal entries debit the expense or other account entered on an invoice distribution line. 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‟. Payment journal entries debit the liability account and credit the cash account of the bank account used to pay an invoice. you can submit this program to change invoice distribution GL dates to the first day of the next open period so you can close the current period. Attention: The generated journal batch needs to be posted from within Oracle General Ledger if the mode of accounting was „Final‟. and can be used to verify that the total invoice amount equals the total invoice distribution amount. from Oracle Payables. and your accounting practices allow you to change invoice distribution GL dates. The following reports can be run to review the invoices and payments that were posted to Oracle General Ledger. Submit the Unaccounted Transactions Sweep Program The Unaccounted Transactions Sweep Program transfers unaccounted transactions from one accounting period to another. This report also provides any errors that may have occurred during generation of the journal entries. 6. creating journal entries for these invoice and payment transactions. c) The Posted Payments Register This report is used to review the payments posted to Oracle General Ledger during a particular accounting period. for the period that is to be closed. Because you cannot close a Payables period that has unaccounted transactions in it. 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. i. and can be used to review the payment activity for each bank account used during that period. The report lists each Accounts Payable Liability Accounting Flexfield and the invoices posted to the account. unless you have modified the SLA rules to create alternative accounting entries to address your specific business needs. Oracle Financials E-Business Suite Release 12 Period End Procedures 25 . The Create Accounting process transfers data to the General Ledger tables. the current accounting period. 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”. you have invoices for which you cannot resolve holds before the close. a) The Subledger Accounting Program Report generated by the Create Accounting program.

To create successful accounting entries for accounted transactions with errors. 8. You can then close the current accounting period in Oracle Payables.) • Sweep 3. The program transfers unaccounted transactions to the period you specify by updating the GL dates to the first day of the new period. Choose the Exceptions button in the Control Payables Periods window. You can also 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 9. Payables automatically produces the Unaccounted Transactions Sweep report. The Subledger Period Close Exceptions Report lists all accounting events and journal entries that fail period close validation. correct any accounting errors and resubmit the Create Accounting Process. 4. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or untransferred journal entries. Accrue Uninvoiced Receipts (Refer to Chapter 7 Period-End Procedures for Oracle Purchasing) 10. From the window you can choose the following buttons: • Review (This submits the Period Close Exceptions Report. To submit the Unaccounted Transactions Sweep Program: 1. Payables opens the Sweep to Period window. You can accept this default or enter another open period. Reconcile Oracle Payables Activity for the Period a) Run the Open Account AP Balance Listing Report (Accounts Payable Trial Balance*) Oracle Financials E-Business Suite Release 12 Period End Procedures 26 . 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. In the Sweep to Period field. Payables opens a message window. Choose the Sweep button.The „Unaccounted Transactions Sweep Program‟ will not roll forward accounted transactions. 2. In the Control Payables Periods window if you try to close a period that has exceptions then the system enables the Exceptions button. Choose the Submit button to submit the Unaccounted Transactions Sweep Program. Payables provides the next open period. or accounted transactions with errors.

prior to running the report.1 and 553484. For reconciliation of Oracle Payables and Oracle General Ledger when posting is only performed at period end. Please refer to the My Oracle Support note # 604739. for a specific accounting period. This report can be used to generate payables trial balance. This report should NOT be used for Payables. In R12. 3. it should be disabled in R12. Please refer to the My Oracle Support note # 553484. use the applicable Payables modified version of the report. This report is a modified version of the Open Account Balance Listing report.Invoice journals must be posted in general ledger to appear on this report. 2. the following reconciliation method can be used: Use the following reports to reconcile your transferred invoices and payments to ensure that your Trial Balance accurately reflects your accounts payable liability: Open Account AP Balance Listing Report or Accounts Payable Trial Balance (for last day of prior period). 4. The report provides details of the outstanding accounts payable liability for the organization. *Accounts Payable Trial Balance report name. Report Name = "Accounts Payable Trial Balance (Old) " Short Name = APXTRBAL This is the R11i Accounts Payable Trial Balance. Payables Posted Invoice Register . this is the correct report name to run if Trial Balance Remodel Phase 4 or higher has been applied.1 to understand which specific report is applicable in your case. Report Name = "Accounts Payable Trial Balance" Short Name = APXTRBAL This is the R12 Accounts Payable Trial Balance. This is run to generate trail balance as of last day of prior period. Oracle Financials E-Business Suite Release 12 Period End Procedures 27 . there are 4 Concurrent Programs related to the trial balance: 1.1 for more details on this report. To obtain the most up-to-date trial balance for a given period. The Open Account AP Balance Listing is based on a Subledger Accounting extract and enables you to identify the open Accounts Payable transactions that make up each Accounts Payable balance. Report Name = "Open Account AP Balances Listing" Short Name = XLAAPRPT This is the subledger Open Account Balance Listing report modified for Payables and should be used as the Trial Balance. with the Oracle General Ledger Creditors Control Account. Instead. journal entries should be posted for the invoice and payment activity for the period.This report basically generates the payables trial balance that can be used for reconciliation of the total accounts payable liabilities in Oracle Payables. Report Name = "Open Account Balance Listing" Short Name = XLATBRPT This is a Subledger Accounting report.

the Posted Invoices Register and Posted Payments Register reports must be run after each posting run. Before running your reports. Open Account AP Balances Report (or Accounts Payable Trial Balance) =0 Attention: When posting to the General Ledger is performed multiple times throughout each accounting period. as SLA has the ability to override the accounting. third party. b) Run Third Party Balances Report (Optional) This report is used to display balance and account activity information for suppliers and customers. run the Transfer Journal Entries to GL Program for all transactions in the period that you are reconciling. for reconciliation of Oracle Payables liabilities with Oracle General Ledger‟s Trade Creditor Control Account. It retrieves the following information: * Third party balances for third party control accounts * Subledger journal entry lines that add up to the total period activity for each control account. you can use the Account Analysis report and the General Ledger reports to determine what journals are being posted to that account. This is run to generate trial balance as of last day of current period) This balancing process will help you ensure that all liabilities recorded in Payables are reflected in the general ledger AP liability accounts.Payment journals must be posted in general ledger to appear on this report. If the balance reported by the Open Account AP Balances Report (or Accounts Payable Trial Balance) does not equal the balance in the AP liability account. For more information refer to „SLA Implementation Guide‟. Oracle Financials E-Business Suite Release 12 Period End Procedures 28 . Open Account AP Balance Listing Report or Accounts Payable Trial Balance (for last day of current period). Attention: A comparison between the accounts in payables with the accounts in GL might not match.Payables Posted Payment Register . and third party site * Third party and third party site information * User transaction identifiers for the associated event The balances in this report can be compared with the general ledger balances for the same control accounts to reconcile. Attention: Typical AP/GL Reconciliation Example 31st March Open Account AP Balances Report (or Accounts Payable Trial Balance) + April Payables Posted Invoice Register –April Payables Posted Payment Register –.30th April. be sure to post the transactions in the general ledger. Also.

Withholding tax is handled by Payables whereas other tax requirements are handled by E-Business Tax. Output from the tax extract is designed to look as close to a simple tax report as possible. and confirmed all invoice holds. Suggested Reports include: Financial Tax Register Oracle Financials E-Business Suite Release 12 Period End Procedures 29 . Run Mass Additions Transfer to Oracle Assets After you have completed all Payables transaction entries. The E-Business Tax data extract draws tax information from each application and stores the data in an interface table. general ledger journal entries imported from SLA are not included in the report. For foreign currency assets. This report is owned by SLA. 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. and carry forwards. After you create mass additions. Run Reports for Tax Reporting Purposes (Optional) A variety of standard reports can be used to provide tax information. 13. you should consider running the Mass Additions Create process on a more regular basis. Review this report. 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. which is required to be reported to the relevant Tax Authority. submit the Mass Additions Create program to transfer capital invoice line distributions from Oracle Payables to Oracle Assets. Optionally compare it with „Third Party Balances‟ report (if applicable). The mass addition line appears in Oracle Assets with the functional currency amount. including withholding tax. 11. It only includes journal entries transferred to and posted to general ledger. Suggestion: If the volume of transactions in Accounts Payable requiring Assets update is large. Note: To avoid duplication with subledger journal entries. 12.c) 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. you can review them in the Prepare Mass Additions window in Oracle Assets. Payables sends the invoice distribution amount in the converted functional currency.

The Key Indicators Report provides current activity indicators that compare current period activity with prior period activity in three major areas: suppliers. and Oracle General Ledger. These tax registers are available: • Tax Register (default) • Interim Tax Register • Nonrecoverable Tax Register These summary levels are available within each Tax Register: • Transaction Distribution Level • Transaction Level (default) • Transaction Line Level Tax Audit Trail Report Use the Tax Audit Trail report to review tax information for posted or partially posted invoices. Run the Key Indicators Report (Optional) This report enables review of the accounts payables department‟s productivity. it includes: Suppliers: Oracle Financials E-Business Suite Release 12 Period End Procedures 30 . payments and matching holds in the system. for each tax rate code. and review the current number of suppliers. The short name of this report is RXZXPFTR. For example. The short name of this report is ZXXTATAT.Use the Financial Tax Register to view the output from the Tax Reporting Ledger. 14. distributions of all posted or partially posted invoices. when combined with similar information from Oracle Accounts Receivable. and payments. This statistical information can be useful for cash flow analysis and forecasting purposes. as well as average values. The Key Indicators Report generates the following reports: a) Key Indicators Current Activity Report Use the Key Indicators Report to review your accounts payable department's productivity. invoices. exception items. When you submit the Key Indicators Report. for each invoice. c) Key Indicators State of the System Report The Key Indicators State-of-the-System Report provides a period-end view of Oracle Payables. The report provides the number of transactions for each indicator (such as number of automatic payments created during a period) and amount values where applicable to the Key Indicator (such as total value of automatic payments created during a period). both the tax amount and the invoice amount subject to tax. This report provides detail tax and invoice information and the total amounts for each tax rate code in the invoice currency and functional currency. The report lists. invoices. The Tax Reporting Ledger consists of accounting information created in Oracle Payables. Oracle Payables produces this report only if you choose „Yes‟ for the Include Invoice Detail parameter. Note: Please refer to Oracle E-Business Tax Reporting Guide for complete details on tax related reports. Payables further breaks down each category into basic items. Oracle Payables generates reports you can use to review payables transaction activity. b) Key Indicators Invoice Activity Report Report that compares the invoice activity for each of your accounts payable processors during the period you specify and the previous period. and updates. The report includes.

Payments: * Number of payments (both manual and computer generated) created and recorded in Payables. * Number of invoice distributions.a payment document can pay multiple invoices). *Average sites per supplier (number of sites divided by the number of suppliers). * Average matching holds per invoice on matching hold (number of matching holds divided by the number of invoices on matching hold).) * Scheduled payments (number of scheduled payments based on payment terms and manual adjustments in the Scheduled Payments tab). * Invoice payments (number of invoice payments made by Payables . Oracle Financials E-Business Suite Release 12 Period End Procedures 31 . * Average lines per invoice (number of invoices divided by the number of distributions. Matching holds: * Matching holds (number of matching holds in Payables). * Average payments per invoice (number of invoices divided by the number of scheduled payments). * Number of supplier sites.* Number of suppliers. * Average invoices per payment (number of payment documents divided by the number of invoice payments). Invoices: * Number of invoices.

* Closed .Period has never been used. while allowing minimum interruption of transaction processing.Period is available for data entry. If the two sets of periods overlap. * Permanently Closed .Period is closed for processing. * Pending Close . * Future Enterable . * Open . you may want to consider using one of the alternate general ledger period conventions. projects may be based on a different periodic cycle to that of the general ledger.This status prevents transaction entry. and transactions are likely to be posted across modules. transactions are summarized into periodic cycles for reporting and reconciliation. Most subledgers have a periodic cycle that parallels the general ledger fiscal cycle. Business Requirements Period end procedures for Oracle Projects have two main functions: Changing the status of the current period to closed Activating all the processes and controls necessary to produce reports that accurately reflect the period activity. Project Periods and General Ledger Periods In Oracle subledgers. such as Projects. then you may need to put in place special procedures for the reconciliation of Projects to the general ledger. However. Suggestion: If you have different periods in Projects. Period Statuses Oracle Projects has statuses similar to the standard period statuses as in other modules: *Never Opened .Period is open to accept transactions from other modules. Project periods may be based on a different period of time such as a week.Chapter 5 Oracle Projects This chapter describes the procedures for performing period-end processing in Oracle Projects Release 12. and other modules. such as a 5-4-4 period split. and allows users to correct unprocessed items prior to completing the period close. Oracle Financials E-Business Suite Release 12 Period End Procedures 32 .No further processing is possible. but can be re-opened if required. Usually used where modules are maintained in different periods. This will enable you to more easily align Projects with General Ledger for reconciliation purposes.

This process needs to be performed for each operating unit defined. then you can run the process “PRC: Sweep Transaction Accounting Events” to change the date on unaccounted transaction accounting events to the first day of the next open GL period. Procedures 1. you should ensure that all the following maintenance activities have been completed: Project Maintenance (revenue/billing based options) * Billing burden schedules and burden schedule overrides * Bill rate schedules and bill rate overrides * Project labor multiplier changes * Revenue budget changes * Project/Task % complete * Funding changes * Changes in the task Ready to Accrue checkbox Implementation Maintenance * Employee assignments Oracle Financials E-Business Suite Release 12 Period End Procedures 33 . This process needs to be performed for each operating unit defined. The Subledger Period Close Exceptions Report lists all accounting events and journal entries that fail period close validation. which allows you to interface and adjust transactions in the period but does not allow transaction entry. without accounting for them. 3.General Exception Handling at Period End If you do not want to correct exceptions during the current GL period. 2. Complete all Maintenance Activities As there are a number of maintenance activities that can affect the period close procedure. Open the Next Oracle Projects Period It is recommended that you open the next period to minimize interruption to users who may require the ability to enter transactions in the new period during the current period close procedure. You can generate the Subledger Period Close Exceptions Report through a concurrent request for the application associated with the responsibility or for all applications in the General Ledger responsibility. Change the Current Oracle Projects Period Status from Open to Pending Close This is an interim status.

d) Run PRC: Update Project Summary Amounts After Resource List Change 5. Run PRC: Compile All Burden Schedule Revisions b) Run organization maintenance to ensure all organizations have been added to all affected compiled burden schedules. the period close. Run PRC: Transaction Import. not during. Run PRC: Add New Organization Compiled Burden Multipliers c) If changes or additions were made to pre-existing resource lists. Transaction Source = Oracle Self-Service Time. Verify that all pre-approved timesheet batches in the current PA period have been released and approved. Run Maintenance Processes It is recommended that the following maintenance processes be run in preparation for the period end: a) Run Burden Schedule maintenance to assure that all burden schedules have been compiled. verify that all timecards are entered or accounted for. If Oracle Projects is the direct data source for payroll or for reconciling labor costs to payroll. update the project summary amounts before. 4. or use function and responsibility restrictions to prevent access to these areas during the period close procedure. Run the AUD: Missing Timecards Report Oracle Financials E-Business Suite Release 12 Period End Procedures 34 . Complete All Transactions for the Period Being Closed Enter and Approve all Timesheets for the PA Period Import all timesheets entered via Self-Service Time. Attention: One rejected expenditure item will cause an entire expenditure to be rejected.* Labor cost rates * Standard costing burden schedule maintenance Other Maintenance * Retroactive changes in employee assignments * Retroactive changes in labor cost rates * Changes in Auto-Accounting Rules or Lookup Sets Suggestion: You may need to implement workflow procedures.

after verifying that all transactions for the period have been accounted for. Run PRC: Interface Supplier Invoices from Payables Interface Expense Reports from Oracle Payables Before generating project revenue or running final cost distribution processes. Access to these activities should be controlled. The following transaction sources are pre-defined.Interface Supplier Invoices from Oracle Payables Before generating project revenue or running final cost event processes. Warning: If your PA period matches a GL/AP month end. Run PRC: Interface Expense Reports from Payables Project Related Inventory Transactions Note: the following processes must be completed within Oracle Inventory prior to importing project related inventory transactions: * Run the Cost Collector * Project Cost Transfer * Run PRC: Transaction Import. import all eligible supplier invoices from Oracle Payables. import all eligible expense reports from Oracle Payables to create pre-approved expense report batches. 6. ensure that all new supplier invoices processing for the current GL period has stopped. Run the Cost Distribution Processes Run all cost distribution processes to cost all enabled expenditures that have an expenditure item earlier than or equal to the current reporting PA period end date: * PRC: Distribute Labor Costs * PRC: Distribute Usage & Miscellaneous Costs * PRC: Distribute Expense Report Adjustments * PRC: Distribute Supplier Invoice Adjustment Costs Oracle Financials E-Business Suite Release 12 Period End Procedures 35 . Source Description Inventory Inventory Misc Work In Process Manufacturing Material Costs Inventory Issues and Receipts entered in the Miscellaneous Transactions window in Oracle Inventory Manufacturing Resource Costs Attention: Entering new expenditures or adjusting existing expenditures during the final cost distribution process may cause reconciliation problems. These expense reports may have been entered via Self-Service Expenses or Expense Reports in Oracle Payables.

Oracle General Ledger and Oracle Assets or revenue to Oracle Receivables before you can change the status of the current PA period to Closed. 7.* PRC: Distribute Borrowed and Lent Amounts * PRC: Total Burdened Cost (If using Project Burdening) * PRC: Create and Distribute Burdened Transactions (If using Project Burdening) Note: PRC: Distribute Expense Report is now obsolete. This program has to be run to generate accounting events. and/or resolved prior to continuing with the period close. Interface CIP Assets to Oracle Assets Run PRC: Interface Assets This process requires that prior to interfacing. or completed more succinctly. which will be later used by SLA. run the mass project revenue generation process. This program is owned by SLA and creates accounting. transfers & posts to GL with the appropriate parameters. Suggestion: Some of the above reports and processes may be run using Submit Streamline Processes. Run the Generate Cost Accounting Events Program This is a new program in R12. Generate Draft Revenue for All Projects After all the cost distributions processes have completed successfully and all supplier invoices have been imported from Oracle Payables. which ensures that processes and reports are run and completed in the correct order. 8. all asset lines have been generated by running the PRC: Generate Assets Lines for a range of projects process. Transfer from Projects to GL can be achieved by submitting the „Create Accounting‟ – (PRC: Create Accounting) process from the SRS screen. Journal Import can be submitted from GL to import the costs into GL. Attention: You can interface asset lines to Oracle Assets only after you have transferred the underlying expenditure items to General Ledger. 6a. For more information refer to Oracle Project Costing User guide. Oracle Financials E-Business Suite Release 12 Period End Procedures 36 . Run PRC: Generate Draft Revenue for a Range of Projects for all projects. Note: Ensure that all interface transaction reports and exception reports are completed successfully. the order of some of the above steps may be changed. If you use the Streamline process. then submit PRC: Submit Interface Streamline Processes with the appropriate streamline parameters to transfer the costs to GL. If accounting was performed without transferring to GL. Interface Cost Transactions to Other Applications You must successfully interface all relevant costs to Oracle Payables. The programs to be run are: PRC: Generate Cost Accounting Events and PRC: Generate Cross Charge Accounting Events.

Attention: Concurrent Revenue processes can be run only if the ranges of projects specified for the processes do not overlap 9. Review and Release Revenue for All Projects Perform a review of the revenue generated and approve the same. 10. Run Generation Revenue Accounting Events Process Run PRC: Generate Revenue Accounting Events to generate events for revenue. These events will be used subsequently by the Create Accounting process to generate accounting. 11. Run Create Accounting to Process Revenue Accounting Events This program is used to generate accounting and then transfer it to the General Ledger based on appropriate parameters. If accounting is generated in FINAL mode with Transfer to General Ledger being set to „No‟ then run PRC: Transfer Journal Entries to GL with parameters to either post in GL or just to leave it unposted. If it is transferred unposted, the General Ledger posting program needs to be submitted. Attention: Interface processes have become obsolete. The same is achieved by PRC: Create Accounting

12. Generate Invoices Run PRC: Generate Invoices to generate invoices to be interfaced to Oracle Receivables. Run PRC: Generate Inter-Company Invoices for a Range of Projects for all projects. This process: * Creates inter-company invoices from cross–charged transactions previously identified by inter-company billing to be processed for cross charging. * Deletes unreleased inter-company invoices. * Creates inter-company credit memos and invoice cancellations. 13. Transfer Invoices to Oracle Receivables Run PRC: Interface Invoices to Receivables Run PRC: Interface Inter-Company Invoices to Receivables

Warning: Make sure that Oracle Receivables has not closed its period until all Oracle Projects invoices have been interfaced to Oracle Receivables

Oracle Financials E-Business Suite Release 12 Period End Procedures

37

14. Run Period Close Exceptions and Tieback Reports Run the period close exceptions reports to identify transactions that have not been fully processed, and that would prevent you from closing the PA period: * AUD: Cross Charge GL Audit * AUD: Missing Timecards * EXC: Transaction Exception Details * EXC: Transaction Exception Summary * PRC: Tieback Invoices from Receivables The tieback process from GL has become obsolete. Review the report generated by Create Accounting/Transfer to GL processes for any errors. Review these reports and make all the indicated corrections. After the corrections are made, run the reports again until there are no exceptions. Suggestion: Some of the above reports and processes may be run using the Submit Streamline Processes process. This process ensures processes and reports are run and completed in the correct order. If you use the Streamline process, the order of some of the above steps may be changed, or completed more succinctly. All the streamline options are not available in R12. Some of them have become obsolete. Please refer to the relevant financials and projects user guides. 15. Run Final Project Costing and Revenue Management Reports Run all of the following project costing management reports: * MGT: Revenue, Cost Budgets by Resources (Project Level) * MGT: Task - Revenue, Cost, Budgets by Resources * MGT: Revenue, Cost, Budgets by Work Breakdown Structure * MGT: Employee Activity Report * MGT: Invoice Review * MGT: Unbilled Receivables Aging * MGT: Agreement Status by Customer 16. Change the Current Oracle Projects Period Status from Pending Close to Closed When changing the status to Closed, the system checks to see if any unprocessed items exist in the period. If unprocessed items exist, the change of status is not allowed. Re-run the period close exception reports to identify any unprocessed items. This process needs to be performed for each operating unit defined.

Oracle Financials E-Business Suite Release 12 Period End Procedures

38

17. Advance the PA Reporting Period (Optional) When you are ready to view the updated summary amounts for the next PA period in the Project Summary Inquiry window, advance the PA Reporting Period. Only one period can be designated as the current reporting period for Project Status Inquiry. The current reporting period does not have to be an open period. 18. Update Project Summary Amounts To enable users to view the latest data in the Project Status Inquiry Window, you must run a final project summary update for the current reporting (pending close) PA period. Attention: The update process cannot run concurrently with the interface processes. Warning: Do not run PRC: Update Project Summary Amounts After Resource List Change during the closing or post-closing processes. 19. Restore Access to User Maintenance Activities After the project summary amounts have been updated for the closed, current reporting period, restore access to user maintenance activities. 20. Reconcile Cost Distribution Lines with General Ledger (Optional) The following Project Subledger Audit Reports print cost distribution lines related to projects. These reports enable you to drill down from a GL account balance in the trial balance to the individual project–related transactions: * Run AUD: Project Subledger Summary * Run AUD: Project Subledger: Detail by Project * Run AUD: Project Subledger: Detail by Expenditure Type 21. Permanently Close the Oracle Projects Period (Optional) When you are satisfied with the closing of the PA period and will not need to reopen the period, change the status of the PA period to Permanently Closed. Warning: Once a period is permanently closed it can never be re-opened.

Oracle Financials E-Business Suite Release 12 Period End Procedures

39

Chapter 6 Oracle Receivables
This chapter describes the procedures for performing period-end processing in Oracle Receivables Release 12.

Business Requirements
Oracle Receivables requires periodic internal reconciliation of the transactions entered into the Accounts Receivables system. Oracle Receivables provides a comprehensive set of reports to facilitate the reconciliation of outstanding customer balances, transactions, receipts, and account balances. The application provides the functionality to enable reconciliation of your sub-ledger, before posting to the General Ledger. Posting to the General Ledger allows the extraction of details from Oracle Receivables, and the creation of journal entries in the General Ledger. After posting to the General Ledger, it is possible to reconcile Oracle Receivables with the General Ledger by verifying that all the correct journal entries were made.

Procedures
The following steps are taken in performing period-end processing for Oracle Receivables. 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 Receivables: * Complete Invoicing, Credits and Adjustments * Complete Receipts and Reversals * Complete Invoice and Customer Import * Complete Lock Box Processing * Run the revenue recognition program (Optional; required if OM-shipping is used) If you import transactions from an external system or Oracle Projects, ensure that you have imported all transactions and master files, and reviewed 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

Oracle Financials E-Business Suite Release 12 Period End Procedures

40

By using the following formula. document number. receivables. AR to GL Reconciliation Report Oracle Financials E-Business Suite Release 12 Period End Procedures 41 . as they are negative on the Transaction Register and positive on the Sales Journal. event type. by account type (i. the general ledger distributions for posted and/or un-posted invoices for the specified period. ledger currency.This report details all the transactions (i.$20 Credits) Attention: The Transaction Register total for any credits must be adjusted. The report also lists in detail. freight. ensure that the Transaction Register matches the Sales Journal: Transaction Register (Items eligible for posting) + 2 * Credit Memo Total = Sales Journal (Debits plus Credits) E. which have been posted in general ledger.e. you can produce a detailed or summary listing of the accounting information you want to review. credit memos. Using the report parameters. tax). and all entries that could not be transferred to the general ledger. and those which are yet to be posted but have been accounted. review the details and make the necessary changes. revenue. Data is then sorted by accounting date. b. using the Sales Journal by Customer report. deposits. category. general ledger journal entries imported from Subledger Accounting are not included in the report. Company. SLA groups the report by ledger. 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. guarantees and chargebacks) entered with a GL date between the period start and period end dates. By altering the parameters. This report details.g. and Transaction Currency. research the customer balances to find out which balance does not tally. specified for the period being reconciled. source. and voucher number. and event class. $100 + (2 * $20) = Debits $120 + Credits $20 ($120 Debits . transactions that have been accounted with error. debit memos. customer name. Note: To avoid duplication with subledger journal entries. The summary totals for the sales journal are by Posting Status. When a transaction is accounted with errors. The total on the Sales Journal by GL Account should equal the total of items eligible for posting as listed on the Transaction Register. the report also lists those transactions. d. Attention: Ensure that the monthly transaction total is accurate and that no distribution issues exist. as accounted by SLA. Journal Entries Report This report enables the review and analysis of accounting entries in the Receivables subledger. This report shows transactions which were entered and completed. If any discrepancies are evident.e. c. invoices.

3. which can be run and reviewed to reconcile these components: Component Beginning Balance Transactions Adjustments Report Aging reports Transaction Register Adjustment Register Oracle Financials E-Business Suite Release 12 Period End Procedures 42 . * Unposted in GL .Journal entries posted to the General Ledger from other subledgers. and * You have reviewed the Unposted Items report to confirm that all journal entries have posted. such as Oracle Payables or a legacy feeder system. using the following formula.The AR to GL Reconciliation report compares the account balances in Oracle Receivables to those in Oracle General Ledger. even if the data matches. thus creating reconciliation issues in Oracle General Ledger. * GL Subledgers Not AR . then the following columns highlight the type of journals that affect the account balances: * GL Source Manual . and * You have used the posting execution reports to confirm that the journal entries exported from Receivables match those posted in General Ledger. known as the Roll Forward Formula: Period-End Balance = Outstanding Balance at Start of 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.Unposted Oracle Receivables journals in the general ledger. During the internal reconciliation process. the journals could still post to incorrect GL accounts. The Difference column indicates how the activity in Receivables compares to the journal source of Receivables in the General Ledger.Manual journal entries made in the General Ledger. However. The Potential Reconciling Items report addresses this issue by suggesting journal items that might potentially post to GL accounts with unexpected account types. 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. If the actual balance of a specific account is different in Receivables than in GL. and highlights journal sources where discrepancies might exist. This report will show a difference between Receivables and GL account balances only if items did not successfully post to GL accounts. Reconcile Outstanding Customer Balances Reconcile the outstanding customer balances at the beginning of a specified period with the ending balance for the same period. use the AR Reconciliation report to confirm that your transactional and accounting data match.

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. on-account amount. payment date. you can review the detailed information on the Receipts Journal Report. and unapplied amount.Exceptions Applied Receipts Invoice Exceptions Report Applied Receipts Register (Identify payments received from customers) Unapplied and Unresolved Receipts Register (identify payments received from customers) Aging report (as of the last day of the accounting period) Unapplied Receipts Ending Balance Attention: You can use the Invoice Exceptions Report to adjust the Transaction Register for any transactions. The Journal Entries Report shows the receipt numbers that contribute to a particular GL account. You can use this report to determine how much your customer owes after taking into account all on-account and unapplied amounts. payment method. you can perform this action by re-querying the receipts and following the normal application procedure. b) Receipt Register Use this report to review a list of receipts for a specified date range. which are not open in Receivables. Receivables displays information about your on-account or unapplied payment such as GL date. Review the Unapplied Receipts Register Use the Unapplied Receipts Register to review detailed information about your customers‟ on-account and unapplied payments for the date range that you specify. Using the receipt number. 5. and therefore do not show up in the aging reports. payment number. If any of the Receipts listed can now be applied to outstanding transactions. batch source. batch name. This report includes both cash and miscellaneous receipts. 4. Oracle Financials E-Business Suite Release 12 Period End Procedures 43 .

it is possible to perform external reconciliation during and after the posting process. Compare this report to the Journal Entries Report (run in Posted status mode) and verify that they match. the entries will have to be transferred separately. Both reports display invoice related receipts and miscellaneous receipts. After internally reconciling the transactions and receipts using these two reports. 6. Account Oracle Financials E-Business Suite Release 12 Period End Procedures 44 . See the following My Oracle Support bugs and enhancement requests for more details: Note 393682. the Receipts Journal Report and Sales Journal display the transactions that would be posted to the General Ledger (provided the posting process was run for the same GL date range). If Create Accounting is submitted in the „Final‟ mode without transferring it to the General Ledger. Reconcile the General Ledger Transfer Process The Create Accounting program produces the Subledger Accounting Program report that shows you the subledger journal entries created for successful accounting events. 8. 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. Reconcile Receipts to Bank Statement Activity for the Period (Refer to Chapter 3 Period-End Procedures for Oracle Cash Management) Attention: The Create Accounting process must be re-run for any miscellaneous accounting entries generated from the bank reconciliation. transactions in error etc. Bug 7423482: Receipt Register and Receipt Journal do not show on-account activity – deemed functionality.1: Unable to Reconcile Receipt Register to Receipt Journal – Enhancement 5567693 is still pending. Bug 7589198: Receipt Register does not match Receipt journal – deemed functionality (similar to Bug 7423482). Oracle Receivables regards these items as having been „posted‟ within the sub-ledger. for transfer to the General Ledger. Once transactions and receipts have been transferred to the GL tables. Create Accounting will generate a report which details the transferred transactions. 7.Attention: 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. The posting process for Oracle Receivables involves a single step: Create Accounting This process can be submitted from the transactions screen to account for a specific receivables transaction or from the SRS screen to account for all receivables transactions. Use the same General Ledger date ranges for the Journal Entries Report and the Create Accounting program. Post to the General Ledger Prior to posting to the General Ledger.

ensure that the consolidated (BFB) invoices have been generated for the current period. Reconcile the Journal Import Process Create Accounting program submits Journal Import automatically when launched in „Mode = Final‟ and „Transfer to GL = Yes‟. 9. 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. the following statements apply: If SLA final accounting lines exist. Attention: Where there are multiple operating units within the same ledger all operating units must be ready to close at the same time. refer to the Oracle Receivables Implementation Guide or the Oracle Receivables User Guide. Reconcile the Journal Import by manually reviewing the transactions in the Subledger Accounting Program Report. they can run Journal Entries Report using Sequence Ranges created in the Create Accounting program run. Attention: If the customer is using Reporting/Accounting sequences. ensure all the invoices generated during the month have been printed and issued. If SLA accounting lines do not exist. the Receipts Journal Report (in „transaction‟ mode) and the Journal Entries Report for posted items. No or ALL. Oracle Financials E-Business Suite Release 12 Period End Procedures 45 . Close the Current Oracle Receivables Period Close the current period in Oracle Receivables using the Open/Close Accounting Periods window. If the Balance Forward Billing functionality is used. Print Invoices Once you are satisfied that the customer balances are reconciled. 11. then AR distribution accounting is displayed. Attention: The „Detail by Account‟ version of the Journal Entries Report may be the most useful for reconciliation in this case. then SLA accounting is displayed. Note: Balance Forward Billing replaces consolidated billing invoices (CBI) feature of 11i. When running any Oracle Receivables reports that display accounting involving transactions that have been posted to GL. The account totals in the Sales and Receipt journals should match the corresponding account balances in the Journal Entries Report. that period is opened for all operating units within the ledger. 10. For more information on the setup of balance forward billing. All of the operating units that share a ledger also share the same period statuses. and compare the total with the Journal Import Execution Report. and comparing them with the Journal Entries Report output. which users can copy and modify the report template according to their needs.balances for transactions and receipts can be reconciled by generating the Sales Journal by GL Account Report. When you update the period statuses to „Open‟ in one operating unit.

If there are any items not posted for the current or prior periods. and third party site * Third party and third party site information * User transaction identifiers for the associated event The balances in this report can be compared with the General Ledger balances for the same control accounts to reconcile. 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. submit with a GL date range for at least the current financial year. Third Party Balances Report Run Third Party Balances Report from the SRS screen. for the transactions. 15. Reconcile Posted Journal Entries After running the GL posting process in Oracle General Ledger. The output will consist of all items not posted to the General Ledger for the specified GL date range. It retrieves the following information: * Third party balances for third party control accounts * Subledger journal entry lines that add up to the total period activity for each control account.12. This report is used to display balance and account activity information for Suppliers and Customers. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or un-transferred journal entries. 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. 14. 16. 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. Run the request from the Submit Requests window. which were transferred in FINAL mode and with Post in GL being set to NO. Using the Submit Requests window to generate this report. run the Journal Entries Report (with „Posted = Y‟) to help reconcile the posted journals. You can also 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 13. It only includes journal entries transferred to and posted to the General Ledger. Oracle Financials E-Business Suite Release 12 Period End Procedures 46 . third party. then re-open both appropriate Receivables and General Ledger Periods and initiate another posting. This report should not generate any output if all Receivables transactions have been successfully posted to the General Ledger.

Note: To avoid duplication with subledger journal entries. Output from the tax extract is designed to look as close to a simple tax report as possible. The E-Business Tax data extract draws tax information from each application and stores the data in an interface table. 18. 17. which is required to be reported to the relevant Tax Authority.Review this report and compare it with the Third Party balances report. Open the Next Oracle Receivables Period Open the next period in Oracle Receivables using the Open/Close Accounting Periods window. The following tax registers are available: a) Deferred Output Tax Register b) Recoverable and Non-Recoverable Tax Registers c) Single Cross Product Tax Register d) Standard Input and Output Tax Registers The following summary levels are available within each Tax Register: * Transaction Header * Transaction Line * Accounting Line Oracle Financials E-Business Suite Release 12 Period End Procedures 47 . General Ledger journal entries imported from Subledger Accounting are not included in the report. including withholding tax. Run Reports for Tax Reporting Purposes (Optional) A variety of standard reports can be used to provide tax information.

or are FYI notifications only (e. Oracle Financials E-Business Suite Release 12 Period End Procedures 48 . The Confirm Receipts workflow sends notifications for items with a Destination or Deliver–To Type of Expense. notify approver approval required). You can also use the report when negotiating with a supplier by limiting the commitments to a specific supplier. a Routing of Direct Delivery. notify requestor requisition has been approved). Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed. Business Requirements The purchasing activity must be reconciled for the accounting period that is to be closed. You can use the report sorted by buyer to monitor buyer performance. Complete all transactions for Oracle Purchasing: a) Complete Requisitions b) Complete Purchase Orders and Releases c) Complete Receipts and Returns Submit the Confirm Receipts Workflow Select Orders process in Purchasing to send notifications through the Web. Closing FYI notifications is Optional. Users should close all FYI notifications and respond to those that require a response. 1.g.Chapter 7 Oracle Purchasing This chapter describes the procedures for performing period-end processing in Oracle Purchasing Release 12. and a Need–By date that is equal to or later than today‟s date. Procedures The following steps are performed while closing the period in Oracle Purchasing.g. and the next five periods. d) Print or Archive all new Purchase Orders e) Respond to all Workflow Notifications Notifications may either require action (e. Review the Current and Future Commitments (Optional) Run the Purchase Order Commitment by Period Report: The Purchase Order Commitment by Period Report shows the monetary value of purchased commitments for a specified period. Requestors can create receipt transactions by responding to the notification. or Notification Details Web page (accessible through the Notifications Summary menu in Purchasing) to requestors or buyers who create requisitions in Purchasing or iProcurement. 2. e–mail.

Check With Suppliers For purchase orders not received. Warning: Where you have Oracle Inventory installed. the receipt transaction needs to be entered by the appropriate personnel. Oracle Financials E-Business Suite Release 12 Period End Procedures 49 . but the receipt has not been entered into Oracle Purchasing. Simply backdate the receipt date when entering receipts for a closed period. to follow up the status of the ordered items with the suppliers. Identify and Review Un-invoiced Receipts (Period-End Accruals) Run the Un-invoiced Receipts Report to review receipts for which the supplier invoice has not been entered in Payables. using the details from the Un-invoiced Receipts Report. If the goods have been received. for what amount. where possible. 6. Entering of invoices. make sure that all receipts have been entered for a specific period. the appropriate department can then follow up with the supplier. It is not necessary to enter all the receipts for a period prior to closing that period. This report indicates exactly what has to be accrued. Attention: Where you have selected to accrue receipts at period end. Receipt accruals can be reviewed by account and by item.3. Review the Outstanding and Overdue Purchase Orders (Optional) Run the following reports: * Purchase Order Detail Report * Open Purchase Orders (by Buyer) Report * Open Purchase Orders (by Cost Center) Report These reports can be used to review all. to enable the creation of receipts accrual entries. The quantity ordered and quantity received is displayed so the status of the purchase orders can be monitored. or planned purchase orders. and helps in the preparation of accrual entries. Follow Up on Outstanding Invoices For any items identified to have been received but not invoiced. it is not possible to process a receipt to a closed Purchasing period. 4. matching of unmatched invoices. before creating receipt accruals for that period. Follow Up Receipts . specific standard. Performing the Oracle Payables Period-End process effectively prevents any further invoices or payments being entered into Oracle Payables for the closed period. which corresponds to the Oracle Purchasing period being closed. should be carried out at this point in the periodend process. Complete the Oracle Payables Period-End Process Complete the steps to close the Oracle Payables period. 7. the appropriate department can use the details obtained from the Purchase Order Detail Report. 5. and resolution of any invoice holds.

Reversal of accrual entries for the next period will happen automatically if: * The Profile option „GL: Launch Auto Reverse after Open Period' is set to 'Y' * And the reverse option is selected for the accrual journal category. Attention: The Receipt Accruals Period End Program creates accounting in the receiving sub ledger only. Attention: This step is only required if the Accrue Expense Items flag is set to Period End. another journal entries batch is created. Reconcile Accrual Accounts . debiting the charge account and crediting the Expense AP Accrual Account. Oracle Purchasing creates an un-posted journal entry batch in the General Ledger for the receipt accruals. This process can be run as many times as needed.Period-End Report to create period-end accruals for uninvoiced receipts. Run the Receipt Accruals . which in turn will trigger the journal import. for Expense distributions for a specific purchasing period. The Create Accounting Program has to be run to create SLA journals. If encumbrance or budgetary control is being used. 9. Oracle Purchasing creates accrual entries only up to the quantity the supplier did not invoice for the partially invoiced receipts. If the profile option is set to „N‟. then the accrual entries need to be reversed manually. Journal entries are created for the amount of the receipt liabilities. a reversal is not required. on the Accrual tabbed region of the Purchasing Options window for the current Organization. If encumbrance or budgetary control is being used.Period End Process Run the Receipt Accruals . corresponding to the encumbrance reversal entries for the un-invoiced receipts that were accrued.8. Each time the process is run. Identify the purchasing period for the receipt accrual entries: Oracle Purchasing creates receipt accruals for all receipts entered up to the end of the nominated period.Perpetual Accruals Identify the period-end balances of the following accounts in the General Ledger: * Purchase Price Variance * Invoice Price Variance Account * AP Accrual Account Oracle Financials E-Business Suite Release 12 Period End Procedures 50 . Oracle Purchasing reverses the encumbrance entry when creating the corresponding accrual entry. When the Accrue Expense Items flag is set to At Receipt.

Manually remove the Invoice Price Variance amount from the AP Accrual Account using your General Ledger. work in process. distinguish accrued receipts from invoice price variances. The Accrual Reconciliation Reports are used to analyze un-invoiced receipts. Identify the Invoice Price Variances amount and Accrued Receipts amount in the AP Accrual Account. At any given time. Oracle Financials E-Business Suite Release 12 Period End Procedures 51 . and identify errors. All the affected PO distributions (in the case of AP/PO transactions and individual transactions in the case of miscellaneous transactions) will be deleted first and the transaction information for these distributions will be fetched and loaded into the accrual reconciliation tables. Identify the invoice price variance for all purchase orders charged to the Inventory AP Accrual Account and compare it with the balance of the Invoice Price Variance account in the General Ledger.* Inventory Account . inventory. Run the Invoice Price Variance Report for the current period. and to reconcile the balance of the AP accrual accounts. the following transactions can account for the balance in the AP accrual account: * Uninvoiced Receipts * Over-invoiced Receipts * Errors (Invoices or inventory transactions charged to this Account by mistake) You need to analyze the balance of the AP accrual accounts. These reports enable you to identify the following issues in receiving. purchasing.(Refer to Chapter 8 Period-End Procedures for Oracle Inventory) Reconcile the balance of the Purchase Price Variance account using the Purchase Price Variance Report. or accounts payable transactions: * Quantity differences between receipts and invoices * Incorrect purchase order or invoice unit prices * Discrepancies in supplier billing * Invoice matched to the wrong purchase order distribution * Receipts against the wrong purchase order or order line * Miscellaneous inventory or work in process transactions that do not belong to the accrual accounts * Payables entries for tax and freight that do not belong to the accrual accounts The Accrual Reconciliation Report Group consists of one program and three reports as discussed below: a) Accrual Reconciliation LR Program load run This program is used in the accrual reconciliation process to populate the accrual reconciliation table with all the necessary transaction data to perform the reconciliation process.

Prerequisites: * Oracle Payables and Oracle Purchasing installed. Attention: Most commercial installations accrue expense receipts at period end. If expense purchases are accrued on receipt. more entries must be reconciled in the AP accrual accounts. the Accrual Reconciliation Report also displays any inventory or work in process transactions for the accrual accounts. You can accrue both expense and inventory purchases as you receive them. When Oracle Payables creates the accounting for the matched and approved invoice. and price differences. After researching the reported accrual balances. these differences are resolved. Accounting entries have to be created in SLA and GL for these write-off transactions by submitting the Create Accounting program.b) AP and PO Accrual Reconciliation Report The AP and PO Accrual Reconciliation Report provides a transactional breakdown of each accrual account with a net balance not equal to zero. Oracle Financials E-Business Suite Release 12 Period End Procedures 52 . * If you have installed Oracle Inventory or Work in Process. the Receiving Value Report by Destination Account must be run to break out the receiving/inspection value by asset and expense. If you also receive inventory. and hence manual adjustment of accrual entries is not required. The Reconciliation reports also provide information on the quantity differences (between the quantity received for a purchase order shipment and the quantity invoiced). Ensure that prior to closing the period. * If expense purchases are accrued at period end. When this happens. and inventory receipts are not performed. Oracle Payables clears the AP accrual accounts. records the liability from the supplier site and helps you monitor potential problems with purchasing and receiving activities that can affect the accuracy of your AP Accrual Accounts. you temporarily record an accounts payable liability to your expense or inventory AP accrual accounts. The Reconciliation Reports can help in monitoring potential problems with purchasing and receiving activities that can affect the accuracy of the AP accrual accounts. c) Miscellaneous Accrual Reconciliation Report The Miscellaneous Accrual Reconciliation Report shows all inventory and AP (not matched to PO) transactions that have hit the accrual account. * If expense purchases are accrued on receipt. d) Summary Accrual Reconciliation Report The Summary Accrual Reconciliation Report can be used to analyze the balance of the AP accrual accounts. no information will be available to report. this report enables reconciliation with the accounts payable accrual account. the Accrual Write-Offs window can be used to indicate which entries are to be removed and written off from this report. as the information is not required as the receipt occurs.

if the encumbrance option for requisitions or purchase orders has been enabled. 10. Mass budget processing also allows you to combine these budgets. or to a separate budget to identify between current year and carry forward amounts if required.Attention: For Oracle Purchasing. Perform Year End Encumbrance Processing (Optional) Oracle Financials provides a number of facilities for the processing of outstanding encumbrances as part of year end processing. and Oracle Work In Progress. * Carry forward the funds available as at the end of the year. a GL transfer or period close must first be performed for the transactions to appear on these reports. * Carry forward encumbrances. For Oracle Payables. For Oracle Inventory.) The steps required to complete year end encumbrance processing in Oracle Purchasing are: a) Identify Outstanding Encumbrances Print the Encumbrance Detail Report to review the requisition and purchase order encumbrances. * Carry forward budgets into the current appropriation budget. The Accrual Reconciliation Reports requires the transactions to be transferred to the General Ledger interface to ensure that the report balances to the General Ledger. The default processing for Oracle Financials at year end is to extinguish any outstanding encumbrances or unused funds when you close the last period of the Financial Year within Oracle General Ledger. before commencing the year end Encumbrance processing in Oracle General Ledger. and requisitions and purchases have entered and approved. Attention: You must complete the Year End Encumbrance processing in Oracle Purchasing. Other facilities available: * Use mass allocations to bring forward part of the funds available. all transactions are created in Purchasing and need the GL Transfer Program to be run to transfer to the General Ledger. (Refer to Chapter 11 Period-End Procedures for Oracle General Ledger. The carry forward process enables managers to perform any of the following: * Carry forward encumbrances for existing transactions (purchases / requisitions). journal entries must be created for the invoices. and the encumbered budget. Oracle Financials E-Business Suite Release 12 Period End Procedures 53 . Use this report to review the accounts encumbered.

as well as any of the following: * Document Type * Supplier Name * Accounting Flexfield Range This process will automatically generate a Mass Cancel listing report identifying the following: * Unable to Cancel Requisitions (reasons provided) * Unable to Cancel Purchase Orders (reasons provided) * Partially in Range Documents * Fully in Range Documents Run Mass Cancel When this process is run. use the Encumbrance Detail Report in a way that matches the accounting method: * Receipt accrual . Oracle Purchasing creates journal entries to zero out the encumbrances associated with the cancelled requisitions and purchase orders. After the Receipt Accruals Period-End process is run. b) Perform Mass Cancel in Oracle Purchasing (Optional) Mass Cancel enables the cancellation of requisitions and purchase orders on the basis of user selected criteria. * Period-end accrual . Payables transfers only accounting information for paid invoices to the General Ledger. Oracle Financials E-Business Suite Release 12 Period End Procedures 54 . Based on this report you can identify those transactions that you wish to carry forward into the new financial year. the encumbrances on the Encumbrance Detail Report remain until payment information from Payables is transferred to General Ledger. the encumbrance detail on the report is based on invoice matching information from Payables. When cash-basis accounting is used and the Payables Transfer to General Ledger process is submitted. During the period. Therefore. an automated process transfers the receipt information to General Ledger using the Journal Import Process. not Purchasing or Oracle Payables.The Encumbrance Detail Report reflects activity from General Ledger. Refer below to the steps required to cancel transactions that are not to be carried forward. Upon entering receipt delivery information.Generate the Encumbrance Detail Report at period-end. not on receiving information.Generate the Encumbrance Detail Report as needed when the Accrue at Receipt option is used. * Cash basis .If cash-basis accounting is used. the Encumbrance Detail Report reflects the true period-end receipt information. Define Mass Cancel The Define Mass Cancel window is used to nominate a date range for transactions.

then any references to the supplier in blanket purchase orders. and shipments to wrong locations. rejected. up to a specified number of characters. d) Supplier Service Performance Analysis Report The Supplier Service Performance Analysis Report lists late shipments. special characters. The report ignores case. rejected shipments. b) Suppliers Audit Report Use the Supplier Audit Report to help identify potential duplicate suppliers. Note that when canceling a purchase order. 11. 12. and returned. Close the Current Oracle Purchasing Period Close the current Purchasing Period in the Control Purchasing Periods window. but within the receipt tolerance days or not past due. Payables lists your suppliers in alphabetical order and you can additionally order the report by supplier number. The report inserts a blank line between groups of possible duplicate suppliers. This report also shows if a supplier is on PO Hold. If purchase order information is merged. After duplicate suppliers have been identified. Oracle Purchasing automatically un-marks all the receipts previously accrued to ensure that these receipts can be accrued again if they are still not invoiced in the next accounting period (where you have selected to accrue receipts at period end). This report lists active suppliers whose names are the same. you must initiate Mass Cancel twice. This report is useful for identifying suppliers with quality performance issues. and auto source rules are updated to the new supplier. you have the option of canceling the original requisition at the same time. You have the option to include supplier site address and contact information. Open the Next Oracle Purchasing Period Open the next purchasing period in the Control Purchasing Periods window. they can be combined using Supplier Merge. early shipments. quotations. spaces. Oracle Financials E-Business Suite Release 12 Period End Procedures 55 .Attention: If you wish to cancel both purchase orders and requisitions. The % Open Current is the percentage of the ordered quantity not yet received. for percents accepted. c) Supplier Quality Performance Analysis Report The Supplier Quality Performance Analysis Report can be used to review suppliers' quality performance. etc. The report lists all site names and addresses of each potential duplicate supplier. This report can be used to derive a supplier service penalty by multiplying the days variance quantity by a percentage of the price. 13. Run Standard Period End Reports (Optional) * Suppliers Quality and Performance Analysis Reports a) Suppliers Report Use the Suppliers Report to review detailed information entered for a supplier in the Suppliers and Supplier Sites windows.

For each blanket purchase agreement and planned purchase order created. Purchasing prints the blanket agreement or planned purchase order header information. The Days Variance is calculated as the summation of the date differential (transaction date subtracted from promise date) multiplied by the corrected received quantity (the received quantity plus or minus corrections) for each shipment. if no release exists. using blanket purchase agreements and planned purchase orders. The % Received On Time is the percentage of the ordered quantity received on the promise date or within the receipt tolerance days. The % Received Late is the percentage of the ordered quantity received after the promise date and outside the receipt tolerance days. The Expenditure is the sum of the item line amounts for standard purchase orders for the supplier. Purchasing provides the detail of the releases created against these orders. Blanket and Planned PO Status Report The Blanket and Planned PO Status Report can be used to review purchase order transactions for items you buy. The % Received Early is the percentage of the ordered quantity received before the promise date and outside the receipt tolerance days. all divided by the total corrected received quantity. e) Supplier Volume Analysis Report The Supplier Volume Analysis Report shows the dollar value of items purchased from a supplier. Use the report to compare actual purchase percentages with sourcing percentage. * Analyze Requisitions Requisition Activity Register The Requisition Activity Register shows requisition activity and monetary values. The Actual Percentage is the items expenditure as a percentage of the total expenditure for the date range of the report. * Review Quotation. The result is the quantity per day the supplier is in variance. Purchasing prints the requisitions in order of creation date and prepared name. The Intended Commitment is the total expenditure multiplied by the split percentage entered in the sourcing rules. The report prints the items that are assigned sourcing rules.The % Open Past Due is the percentage of the ordered quantity not received by the promise date and beyond the receipt tolerance days. RFQ and Purchase Order Statuses Purchase Order Statuses may optionally be reviewed early in the period close processing for Oracle Purchasing. * Savings Analysis Reports a) Savings Analysis Report (by Category) Oracle Financials E-Business Suite Release 12 Period End Procedures 56 .

If a quote is not defined. The report includes a price type Legend at the bottom of each page for the price type. and if the line price type is L. the line price was from the Market Price. If the line price type is Q. If the market price is not defined. Purchasing uses the list price. The Actual Amount is the product of the actual price listed on the purchase order line and the quantity ordered. Purchasing uses the list price. The Negotiated Amount is the product of the price on the quotation and the quantity ordered. * Cancellation Reports Use these reports to review all cancelled purchase orders and requisitions.The Savings Analysis Report (By Category) shows buyer performance by category. the line price was from the Market Price. The report includes a price type Legend at the bottom of each page for the price type. The Amount Saved is the negotiated amount less the actual amount. If the line price type is M. If a quote is not defined. * Encumbrance Accounting Reports Encumbrance Detail Report The Encumbrance Detail Report can be used to review requisition and purchase order encumbrances for a range of accounts if the encumbrance option for requisitions or purchase orders has been enabled. The Negotiated Amount is the product of the price on the quotation and the quantity ordered. Use the report to compare the market. Use this report to review the encumbered accounts. the line price was from the List Price. The Amount Saved is the negotiated amount less the actual amount. with negative figures in parentheses. with negative figures in parentheses. The Actual Amount is the product of the actual price listed on the purchase order line and the quantity ordered. the line price was from the Quote. Purchasing prints the product of the market price of the item ordered and the quantity ordered. particularly where you have defined multiple Mass Cancel batches: a) Cancelled Purchase Orders Report b) Cancelled Requisitions Report Oracle Financials E-Business Suite Release 12 Period End Procedures 57 . the line price was from the List Price. quote. If the line price type is Q. Purchasing prints the product of the market price of the item ordered and the quantity ordered. b) Savings Analysis Report (by Buyer) The Savings Analysis Report (By Buyer) shows buyer performance by purchase order. or list price to the actual price. and if the line price type is L. If the market price is not defined. If the line price type is M. the line price was from the Quote. and there are entered and approved requisitions and purchases.

Independently open and close periods for each inventory organization. or are awaiting data entry (e. Business Requirements The period close process for Oracle Inventory enables the summarizing of costs related to inventory and manufacturing for a given accounting period. To avoid date entry error (when both periods are open) there is a profile option „INV: Transaction date validation‟. Optional . “close period status report”. Transfer inventory and manufacturing costs to the General Ledger. shipping. Attention: Usually. and then the closure process is processed for the past month.Cycle Count Pending Approval Report Oracle Financials E-Business Suite Release 12 Period End Procedures 58 . logistic and manufacturing systems need to be always open for worker transactions. packing slips in receiving). which means at month end the next period is opened to allow key-in from the first day. Note: Since Release 12. Perform interim transfers to the General Ledger without closing the period.Chapter 8 Oracle Inventory-Cost Management This chapter describes the procedures for performing period-end processing in Oracle Inventory Release 12. receipts. Oracle Inventory and Oracle Cost Management provide the required features to affect the necessary period-end procedures to: Reconcile the inventory and work in process costs and values. Complete All Transactions for the Period Being Closed Ensure that all issues. and adjustments have been entered and verify that no hard copy records exist. These costs are then transferred to the General Ledger for posting.g. Transfer summary or detail accounting information to the General Ledger. Attention: For environments with a large number of organizations. Procedures The following steps are taken in performing period-end processing for Oracle Inventory: 1. you can open / close many logistic organizations by batch program: “OPSR and CPSR open period status report”. Cost Management becomes an application module holding Inventory/Receiving/WIP accounting entries.

and pending shop floor move transactions existing in this period. Check Inventory and Work in Process Transaction Interfaces Check the Interface Managers window to ensure that there are no unprocessed background or concurrent programs. These must be resolved before the period is closed.2. revenue recognition has been processed in AR. Attention: This process needs to be completed for each defined Inventory Organization. and then relaunch transactions using: * INV / Transactions / Pending transactions * INV/ Transactions / Transaction Open interface * OM / Shipping / Interfaces This check should be done during the month to avoid cumulative problems at month end before closing. uncosted material transactions. This will display transactions under the following statuses: * Resolution Required: Displays the number of unprocessed material transactions. The interface managers that need to be run are as follows: * Cost Manager (mandatory) * Material Transaction Manager (Optional. Since a period. For this purpose you need to run these 2 concurrent programs: * “Collect Revenue Recognition information” * “Generate COGS Recognition event” Run the „Create Accounting-Cost Management‟ program up to the period end date before closing the period. running this process prior to closing the period facilitates validating the interface transactions. once closed. Oracle Financials E-Business Suite Release 12 Period End Procedures 59 . Transfer Summary or Detail Transactions If Order Management is used. Check and fix pending Transactions Check and fix any rejected transactions from the Inventory Accounting Period Window: click on the pending button to display pending transactions. and the accounting entries between „Deferred COGS account‟ and „COGS account‟ must be generated in INV-CST. * Resolution Recommended: Displays the number of pending receiving transactions. pending material transactions. and pending IWIP costing transactions existing in this period. Though the accounting period can be closed. 4. once it is closed these transactions cannot be processed in that period. In case of error. depending on INV profile option “TPINV: Transaction Processing Mode”) * Move Transaction Manager (for IWIP) 3. Any adjustments to the period can be made via new inventory transactions as required. correct the error at the source. cannot be re-opened. for the order-shipments which have been invoiced in AR.

Attention: The Transfer Journal Entries to GL Cost Management Program transfers the accounting details for all the inventory organizations within a Ledger. Errored can be selected). 5. Attention: If this step was by-passed. The period close performs the following: * Closes the open period for Oracle Inventory and Oracle Work in Process. 7. But no adjustments to that period can then be entered. This still allows miscellaneous transactions corrections in inventory. If Oracle Purchasing or Oracle Inventory are closed. As explained in step 3 above.If the Create Accounting Program is run in Final Mode without transferring to GL then run the „Transfer Journal Entries to GL Cost Management‟ which transfers the accounting to GL. Draft Accounted. Attention: This process needs to be completed for each defined Inventory Organization. to enable the running of purchase accruals to accrue expenses on un-invoiced receipts. as a manual procedure.g. since transactions cannot be posted to a closed period. Open the Next Inventory Period Prior the first day of data entry. and accounting events by accessing the Sub ledger Accounting user interface from the View Transactions window and various statuses (e. and the period was closed. and a closed period cannot be re-opened. Oracle Purchasing should be closed before Oracle Inventory. a GL Transfer would automatically be initiated. prior to closing the inventory period. journal entries associated with transactions. Close the current Oracle Payables and Oracle Purchasing Periods Complete all steps required to close Oracle Payables and Oracle Purchasing. However. open the next inventory period using the Inventory Accounting Periods window. View accounting. Final Accounted. Oracle Payables is closed prior to closing Oracle Purchasing. * Creates summary or detail inventory accounting entries in the GL interface. Oracle Financials E-Business Suite Release 12 Period End Procedures 60 . * Creates summary or detail work in process accounting entries in the GL interface. a receipt cannot be entered for that period. Attention: This process needs to be completed for each defined Inventory Organization. 6. click on the pending button to display any remaining pending transactions and make the appropriate resolutions. Close the Current Inventory Period Closing the inventory period using the Inventory Accounting Periods window automatically transfers summary transactions to the GL interface table.

or the Elemental Inventory Value Report. including variance calculations. Use the Period Close Value Summary Report to see summary balances for subinventories. Oracle Financials E-Business Suite Release 12 Period End Procedures 61 . This. Warning: Closing an inventory period permanently closes the period and no further transactions can be charged to that period. The period-end values by sub-inventory are reported in the Period Close Summary Report. the period close process writes off any remaining balances and transfers any period costs to the General Ledger. The period close process automatically transfers all job costs and variances by GL account. Finally. If you run this report for a closed accounting period. Discrete jobs and certain non-standard jobs are closed separately. along with the values in transit creates the period-end value for the current period. the period close adds the net transaction value for the current period to the previous period‟s ending value. (Warning : these reports show the value at the point in time you run the report). use this report to reconcile an account across several periods. use the Material Account Distribution Detail Report to print the transactions in detail. 8. b) Material Account Distribution Summary Report. If you detect unusual accounts or amounts.* Calculates period-end sub-inventory balances. b) Material Account Distribution Detail Report Use the Material Account Distribution Detail Report to view the accounts charged for inventory transactions. For each sub-inventory. The balance normally matches with the GL balance. and detailed item information for the sub-inventories specified. the report displays the sub-inventory values at the end of that period. Additional useful reports: a) Inventory Value Report You can see more sub-inventory balance details by running the Inventory Value Report. valuation. Run Standard Period-End Reports and reconcile the Perpetual Inventory with GL Check that the perpetual inventory value up to the end of the period being closed matches the value reported in the General Ledger. If you run the report for an open period. For expense non-standard jobs. The following reports can be run to help with these reviews: a) Period Close Value Summary Report. Use the Material Account Distribution Summary Report to verify inventory account activity against inventory valuation increases or decreases for the accounting period. Review inventory transaction values transferred to the General Ledger by GL batch. Job close performs the necessary accounting for each job. the report displays the sub-inventory value at the point in time you run the report. may create discrepancies. But Journal entries from products other than Oracle Inventory. These show quantity.

Validate the Work in Process Inventory If Oracle Work in Process is installed. and orders the transactions by earliest transaction date. and scrap. overhead and outside processing charges. The WIP Account Distribution Report lists detailed account information for work in process cost transactions. Detailed account information is available for specific accounts. by transaction type. or both to help reconcile the General Ledger. Oracle Financials E-Business Suite Release 12 Period End Procedures 62 . completions. This information can be found using the Material Account Distribution reports in Oracle Inventory. by summary or detail. check the work in process inventory balances against transactions with the WIP Account Distribution Report. The system groups the transactions by job or schedule. and period close and job close variances. GL batches.9. including resource. cost updates. This report does not list material cost transactions such as issues.

Business Requirements At period end. 1. Completing all transactions for Oracle Assets: * Prepare and Post Mass Additions * Complete Manual Additions * Complete Adjustments * Complete Retirements * Complete Transfers * Complete Reinstatements 2. it cannot be re-opened. Assign All Assets to Distribution Lines If an asset has not been assigned to a distribution line. and will not close the period. Check that transactions are not being entered as Oracle Assets prevents transaction data entry while the Depreciation Run Process is running. 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.Chapter 9 Oracle Assets This chapter describes the procedures for performing period-end processing in Oracle Assets Release 12. Once a depreciation period in Oracle Assets has been closed. the period end Depreciation Process will not complete. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed. Oracle Assets has only a single open depreciation period in each asset book. 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 Oracle Financials E-Business Suite Release 12 Period End Procedures 63 . Accounting can be created for Fixed Assets (FA) transactions and sent to GL on a continual basis throughout the period using the Create Accounting program after the introduction of SLA. run depreciation for each asset book set up for the enterprise. Procedures The following steps are taken in performing period-end processing for Oracle Assets.

Oracle Financials E-Business Suite Release 12 Period End Procedures 64 . depreciation. Oracle Assets does not close the period. The Run Depreciation process will close the current depreciation period and open the next only if the Close Period checkbox is selected. using the Submit Requests window. or you can review the Depreciation Program Report via the Requests window. This program replaces the „Create Journal Entries‟ in Oracle Assets. However. The book and depreciation period are nominated on the Submit Request window. By using the depreciation log file. Oracle Assets gives you the option of closing the current period if you check the Close Period check box on the „Run Depreciation‟ window. If the program is run in FINAL mode with POST as yes. you cannot reopen it. Both Reserve Ledger Reports can also be run at any time. If all of your assets depreciate successfully. Oracle Assets automatically closes the period and opens the next period for the book. Create Accounting Submit the Create Accounting process from SRS screen. and reporting programs off-line. the Run Depreciation process will end with an error status. When the process is run. Final and Final Post. the retirements process can be run several times during the period to reduce the time for the depreciation process. This process submits concurrent requests to run the calculate gains and losses. 4. Once the program closes the period. Alternatively. the Calculate Gains and Losses program will be submitted as part of the Run Depreciation Process. If an asset has not been assigned to a distribution line. and then runs the appropriate Reserve Ledger Report. When the depreciation program is run for an Asset Corporate Book. If you do not check the Close Period check box when you run depreciation. then the Tax Reserve Ledger Report is generated. The unassigned assets can then be assigned to distribution lines and the Depreciation process resubmitted. Note: Depreciation will be rolled back automatically if any activity is performed on a depreciated transaction. you can determine which assets were unassigned. This is valid only if the period is not closed. Run Depreciation When you Run Depreciation. 5. This program can be run in 3 modes: Draft. Attention: Ensure that you have entered all transactions for the period before you run depreciation.independently for each depreciation book. For books with a large volume of assets. Oracle Assets automatically calculates depreciation for all assets. calculates gains and losses for all retirements. if the depreciation program is run for a Tax book. The asset book and depreciation period are nominated on the Run Depreciation window. The Depreciation process only processes assets that have not already been processed. the Journal Entry Reserve Ledger Report will be generated. This process generates accounting and also enables transfer to and posting in GL. The Run Depreciation process is performed independently for each asset book.

The depreciation expense journal entries can be created from an Asset Corporate or an Asset Tax book and transferred to the General Ledger. transfers. For more information. Depreciation Projections (Optional) You can project depreciation expense for any number of future periods. Attention: If in 11i the FA Account Generator Workflow was customized. and bonus reserve accounts when you enter prior period additions. bonus expense. In the second case workflow will be used to generate accounts. Create deferred journal entries using the SLA Create Accounting Process. You can run the Create Accounting process as many times as necessary within a period. the customizations will have to be re-implemented using SLA or FA: Use Workflow Account Generation should be set as YES. If the profile is set to „No‟. The GL period for which journal entries are to be created must be open. Warning: Journal entries cannot be created from asset budgeting books. If the program is run in FINAL mode with „Transfer to General Ledger‟ as NO. Attention: „Create Journal Entries‟ program has now been replaced by „Create Accounting‟ program. 8. unlike at Asset Book level as in Release 11i. Rollback Depreciation There is no separate program as in Release 11i to perform the rollback. 6. Results can be summarized by year. please refer to the Oracle Assets User Guide. Create Deferred Depreciation Journal Entries (Optional) Deferred depreciation is the difference in depreciation expense taken for an asset between a tax book and its associated corporate book. create accounting will create accounting based on its rules and the workflow will not be used. By default.then the entries will be automatically posted to the General Ledger. please refer to the Oracle Assets User Guide. or retirements. Journal entries can be created for any period in the current fiscal year for which journal entries have not already been created. on as many as five depreciation books at once. This difference results from the use of accelerated depreciation methods in the tax book. month. 7. accumulated depreciation accounts. Any alteration on a depreciated asset will result in an automatic rollback. Oracle Assets uses the „FA: Use Workflow Account Generation‟ to make a decision on whether to use the workflow or not. on upgrade this profile option is set to „Yes‟. Note: Rollback happens at Asset Level in Release 12. or Oracle Financials E-Business Suite Release 12 Period End Procedures 65 . based on rules and in-built event class/entity model processes for deferred depreciation. There is no need to run Depreciation before creating accounting transactions. then run Transfer Journal Entries to GL – Assets later on. For more details. quarter. This program creates adjusting journal entries to depreciation expense.

Review and Post Journal Entries If accounting was performed without the journal entries being posted. * 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 * Drill Down Reports a) Drill Down Report– Oracle Financials E-Business Suite Release 12 Period End Procedures 66 . 9. use the More Actions button to Post each Journal individually or if the source of Assets has been included in the Auto Post options. b) Tax Reserve Ledger Report Additionally. 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.any specified interval. 10. The results can be summarized also by cost centre or depreciation expense account. the Account Reconciliation Reserve Ledger Report can be run. review the unposted journal entries in the Enter Journals window. the Assets Journals will be posted automatically in the next scheduled posting run. Post each journal entry batch using the Post Journals window in Oracle General Ledger to update the account balances. Optionally. in Oracle General Ledger.

Note: Drilldown is a two-stage process.run the General Journals Report for Posting Status = Posted. b) Account Drill Down Report– Reconcile journal entries to the General Ledger. d) Financial Statements Generator – It is recommended that you create a detailed Financial Statement Generator (FSG) for all asset accounts. 11. 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 Oracle Financials E-Business Suite Release 12 Period End Procedures 67 . b) Posted Journals Report– Run. The report gives detailed information of the asset transactions represents by a journal entry line. c) Account Analysis Report with Payables Detail – The ending balance of this report reconciles with the Reserve Summary Report ending balance.Reconcile the batch totals from this report with those of the General Journals Report in Oracle General Ledger run for posting status = „Unposted’. * General Ledger Reports a) Unposted Journals Report– Run. This can be done at cost centre level for direct comparison with the Asset Cost Summary and Reserve Summary reports. then your financial statements will also be inaccurate. The report enables detailed review of the account activity on a specific general ledger account.run the General Journals Report for Posting Status = Unposted to reconcile with the Drill Down reports. Run Responsibility Reports (Optional) It is also important to ensure that your asset inventory is accurate. From SLA drilldown can be performed to transaction level. In the first stage drilldown happens from GL to SLA. If the asset inventory is inaccurate.

Complete Daily Trading Activities Complete trading activities for the day. Revaluation is an optional step in the accounting process. foreign exchange transactions and derivatives. for all money market products. * Choose the Calculate button. Oracle Financials E-Business Suite Release 12 Period End Procedures 68 . you must perform revaluations as part of the accounting process. rather than as an accumulating amount for multiple periods. Oracle Treasury facilitates settlement. Once your financial transactions are captured in the system. valuation. * Choose a period or an existing Batch ID. Reversal entries are not required. 3.Chapter 10 Oracle Treasury This chapter describes the procedures for performing period-end processing in Oracle Treasury Release 12. manually or automatically. * Navigate to the Accruals window. Business Requirements Oracle Treasury is a comprehensive treasury solution that helps you effectively manage your investments. 2. If you set the „Accounting Perform Deal Revaluations company parameter‟ to Yes. Procedures The following steps are taken in performing period-end processing for Oracle Treasury. accrual and accounting for these transactions. Amortization and accruals adjustments are calculated incrementally for each batch period. 1. validate them. and send payment instructions to the bank. if necessary. split by revenue and expense. Perform Revaluation 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. Generate Accruals and Amortization You can generate amortizations and accruals adjustments. These adjustments include amounts for settling derivatives. * Choose a Company. debt. such as Forward Rate Agreements (FRAs) and options. You can automate steps 2-5 by running the Accounting Streamline Process concurrent program.

and reallocate suspense journal entries to a GL account. change the dates or GL accounts for your journal entries. 5. 4. you cannot change any of the accounting for the batch in Treasury. If you find the results to be incorrect.* The accrual and amortization details for the financial transactions in the specified period appear. view the generated journal entries. re-create the accruals. use the Transfer Journals to GL window to transfer your journals from Treasury to General Ledger. Once you transfer your daily journals to General Ledger. * Authorize the results. Treasury sends the journals directly to GL and not via SLA. but you cannot change them. Transfer Journals to General Ledger After you enter and verify all accounting changes for the journal. Oracle Financials E-Business Suite Release 12 Period End Procedures 69 . delete them and review the corresponding financial instrument. Attention: There is no integration yet with SubLedger Accounting (SLA). Generate Journals Use the Daily Journals window to generate the daily journals for an accounting batch. You can view and delete these period adjustments. Once the financial instrument is correct.

A closed period can be re-opened (provided it has not been permanently closed). The periods can then be permanently closed as required. if it is necessary to enter or modify accounting transactions for that period. but can re re-opened if required. Managers have the discretion to immediately close a period to prevent unauthorized processing. Note: The Period-End and Year-End processes are the same if Encumbrances are Not Used. * Permanently Closed . and transactions are likely to be posted across modules. * Open . then the steps detailed below will need to be completed for both your accrual and cash Ledgers. For most modules you can view and select one of the following: * Never Opened . but be able to re-open periods for post processing adjustments. an accounting period is closed after all the accounting transactions have been completed for the period. * Future Enterable . Combined Basis Accounting If you have installed combined basis accounting. Oracle Financials E-Business Suite Release 12 Period End Procedures 70 .The period is open to accept transactions from other modules. Business Requirements Period End Close In Oracle General Ledger. This will mean that you will need to select the responsibility relevant to both Ledgers when completing these tasks. Suggestion: Periods are usually only „finally closed‟ when all adjustments and reporting requirements for the prior financial year are finalized.Period is closed for processing.The period has never been used. independent of the period/year end process. Usually used where modules are maintained in different periods.Chapter 11 Oracle General Ledger This chapter describes the procedures for performing period-end processing in Oracle General Ledger Release 12. these tasks could be performed from a single responsibility.Period is available for data entry * Closed . Depending on the Ledger set/Data Access Set attached to a responsibility. Special steps are required for Encumbrances.No further processing is possible.

and journal entry line level. updates the GL_BALANCES table. run in Oracle General Ledger.in the GL_INTERFACE table. * Delete any error journal entry batches. journal entry level. Inventory. Simply re-enter the source from which journal entry batches are to be imported. Treasury and Projects) have been transferred to Oracle General Ledger. * Re-import these corrected journal entry batches from the GL_INTERFACE table. Purchasing. Ensure that the accounting information from the sub-ledgers (Oracle Payables. and GL_JE_LINES tables. review the Journal Import Execution Report to identify which journal entry batches were not successfully imported. and is run automatically. except at year-end. into Oracle General Ledger. Maintain period-end exchange rates for all foreign currencies to which you want to translate. Receivables.Procedures The following steps are taken in performing period-end processing for Oracle General Ledger. when the profile option „SLA:Disable Journal Import‟ is set to „No‟. Cash Management. This process populates the GL_JE_BATCHES. Journals are comprised of batch level. * Make the necessary corrections . Run Create Accounting program or the appropriate program (based on previous runs of Create Accounting) to transfer data from subledgers. Attention: The journal posting process. GL_JE_HEADERS. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger Journals are created to load accounting information into Oracle General Ledger. 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. Determine the source(s) for these error batches. The Create Accounting process of SLA submits Journal Import Process (based on appropriate parameters as discussed in previous sections). 2. so that there would not be any data left in the GL_INTERFACE table. via the Correct Journal Import Data window. Journal Import: * If not automatically completed. prior to opening the first period of the new financial year. and retrieve the run ID from the Journal Import Execution Report. Order Management. Oracle Financials E-Business Suite Release 12 Period End Procedures 71 . information. data will be rolled back to SLA tables. 1. Note: If journal import fails when importing from the sub ledger modules. it is recommended that you complete all period end processing. At year-end. Assets.

Update journal entries as appropriate. Oracle Financials E-Business Suite Release 12 Period End Procedures 72 . Submit the process to generate the Recurring Journals. Note: If you are loading accounting journals for 3rd party systems directly to Oracle General Ledger. non-Oracle subledgers has been transferred to Oracle General Ledger. Post step-down allocations in the correct order (i. Review and Verify Journal Details of Unposted Journal Entries Review any remaining unposted journal entries for the current period. for each successive level of allocation entry).e. prior to generating the journal.Attention: Leave sufficient time to re-import any journal entries not successfully imported from the feeder systems. This process can be run across ledgers and across currencies. 6. Generate Reversal Journals (Optional) Select all the Journals to be reversed. * Run the Journal Import process for these sources and ensure the resulting Journal Entries are posted either automatically by AutoPost or manually. Generate Mass Allocation Journals (Optional) Select the Mass Allocation Journals that require generation for the current period. the accounting journal details will automatically by stored in the XLA tables. 5. perform the calculation and post. Generate Recurring Journals (Optional) Select all the Recurring Journals that require generation for the current period. use the GL_Interface. Then update and post them. Submit the process to generate the Reversal Journals. prior to being transferred (in summary or detail) and imported into Oracle General Ledger. This process can be submitted for foreign currency and for multiple ledgers. If you are using Oracle Financials Accounting Hub to generate accounting for your 3 rd party systems. Complete Non-Oracle Sub-ledger Interfaces to Oracle General Ledger (Optional: only required if you want to post from non-Oracle systems) Following the same procedures as for Step 2: * Ensure that the accounting information from any site specific. This process can be run across ledgers. provided the access is available. Ensure that all entries to the source accounting flexfields used in the MassAllocation Journal definitions are finalized for the current period. 8. 3. Upload Journals from Web Applications Desktop Integrator (Web ADI) to Oracle General Ledger (Optional) Journal information can also be imported from spreadsheets into Oracle General Ledger using Web ADI. 7. 4.

including reversal.Entered Currency g) Journals by Document Number Report (when document sequencing is used) 9. Following review of journal entry batches. ensure that the debits and credits equal the control total.Attention: Journal entries can be reviewed on-line. Oracle General Ledger generates this report every time posting of journal entry batches occurs. Post All Journal Batches Post all journal entries for the current period. before posting. or via reports.Line Report e) Tax Journals Report f) General Ledger . recurring and allocation journals. This report indicates any errors in journal entries or journal entry lines were discovered during the posting process. Locate the problems with unpostable journal entry batches using the following information: a) Control Total When using a control total. Reviewing journal entries prior to posting minimizes the number of corrections and changes after posting. Review the results of the post: * The Posting Execution Report facilitates review of the results of journal entry posting. Standard Journal reports available included: a) Journal Batch Summary Report b) Journals . Update unpostable journal entries. c) Batch Status Oracle Financials E-Business Suite Release 12 Period End Procedures 73 . b) Period Status Post Actual batches to open periods.General Report c) Journals .General Report with a Posting Status of Error Journals to review error journal entry batches and their journal entries. Post Encumbrance batches to any period up to the last period in the latest open encumbrance year. perform any journal entry updates.Entry Report d) Journals . including any adjusting entries. * Run the Journals . Post Budget batches to any period in an open budget year.

and ensure a follow-up with relevant colleagues if any exceptions are identified. Custom accounting reports can be created by using the „Financial Statement Generator (FSG)‟. Revalue Balances (Optional) Revalue account balances to update functional currency equivalents. Translate Balances (Optional) Define any new currencies to which accounting balances are to be translated. Detail Trial Balance Report b) Income Statements c) Gross Margin Analysis 11. The General Ledger accounting can run the Period Close Exceptions report to double check that there are no outstanding transactions in the subledgers and GL. it is advisable to create a standard period-end accounting report set that can be run at each period end. Maintain period-end exchange rates for all foreign currencies to which you want to translate.g. discard any obsolete versions of your report for that accounting period. Run the Period Close Exceptions Report This is a new step in Release 12. Request financial reports such as: a) Balance Sheets e. Post updated journal entries. Oracle Financials E-Business Suite Release 12 Period End Procedures 74 . 10.Oracle General Ledger describes the problems with unpostable batches. Suggestion: To prevent confusing different versions of accounting reports for a specific accounting period. Run GL Trial Balances and Preliminary Financial Statement Generator Reports (FSGs) To maintain a consistent audit trail. 9a. 12. and the corrected journal entries re-submitted for posting. Common reasons for unpostable batches are: * Control total violations * Posting to unopened periods * Unbalanced journal entries Attention: All errors in the journal entry batches must be fixed.

Suggestion: To produce financial reports that reconcile your consolidating companies with the consolidated totals. Recurring Journals. * Example of consolidation across ledgers when sharing same COA and Calendar (Using Ledger Set and access granted via „Data Access Set‟): a) Define consolidated FSG b) Perform revaluation and translations across ledgers c) Enter consolidated and eliminating entries d) Report on FSG by selecting the ledger set option while running * Example of consolidation across ledgers using the Global Consolidation System (GCS): Oracle Financials E-Business Suite Release 12 Period End Procedures 75 . Financial Consolidation Hub or the Hyperion Consolidation functionality. d) Define financial statements with the reporting hierarchy. and build reports with a separate column for „consolidating entries‟. enter the consolidating entries to a separate company. * Consolidate within ledgers a) 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 . investments in subsidiaries. Translate account balances to any defined currency. c) Define a reporting hierarchy that consolidates all the companies.use formulas b) Post consolidating journal entries.Maintain average exchange rates for all foreign currencies to which you want to translate. Consolidate Ledgers (Optional) Attention: You can consolidate using Global Consolidation System. 13. use recurring journal entry formulas.define mapping rules to eliminated intercompany receivables. Whichever you choose you can run your extract programs to extract the data from General Ledger to the consolidation systems. intercompany sales etc. Maintain historical rates or amounts for any owner‟s equity accounts to be translated. payables. Suggestion: To automatically generate the amounts and accounts for consolidating and eliminating journal entries.

These reports list beginning and ending account balances and all journal entry lines affecting each account balance. e) Report on this consolidated ledger using FSG‟s. batch name. improved online reconciliation reporting. online reconciliation report provides drill-down to underlying sources and source journals for easy identification of reconciliation differences. f) Analyze results using drill-down capability from Parent ledger to Subsidiary ledger/s. general journals. d) Enter consolidated and eliminating entries. * Review Detail Account Balances On-line * Review Account Balances via Reports Request accounting reports such as general ledgers. trial balances. A new. The report provides detailed information on each journal entry line including source. Review and Correct Balances (Perform Reconciliations) Oracle General Ledger should be reconciled with all other modules. a) General Ledger Reports General Ledger Reports facilitate tracing back each transaction to the original source. b) Perform revaluation and translation of foreign subsidiaries as required. Reconcile Intercompany (optional) Advanced Global Intercompany System in Release 12 provides more advanced features such as automatic generation of intercompany invoices in AP and AR. Adjust journals to correct any errors in the journals. 14.a) Define consolidations. and description. c) Trial Balance Reports Oracle Financials E-Business Suite Release 12 Period End Procedures 76 . Detailed information is provided for each journal entry line. 13a. Create and post adjusting journals to correct errors in account balances. b) Accounts Analysis Reports These reports list the accumulated balances of a range of Accounting Flexfields and all journal entries that affect that range. category and date. which includes the source. and accounts analysis reports to facilitate reconciliation of Oracle General Ledger with the other Financials and manufacturing modules. Attention: All errors in the journal entry batches must be fixed. and is also fully integrated with SLA. and the corrected journal entries re-submitted for posting. c) Run consolidations.

unposted or error journal entries and report on a specific batch or on journal entries from a specific source. Enter Adjustments and / or Accruals and Post To correct errors in account balances made by posting incorrect journals. When the balance for group of transactions is zero you can mark the transaction as reconciled. Determine the adjusting entries required to net these accounts to zero. Oracle General Ledger will not post out-of-balance batches. * Clear Suspense Accounts Examine the General Ledger and account analysis reports to identify the source of entries to the suspense accounts. An incorrectly entered posted journal must be reversed to back-out the accounting of the original posted journal. you can selectively cross-reference transactions in GL with each other by entering reconciliation reference information at the journal line level. d) Journal Reports These reports print journal entry batches and include journal entry subtotals. Attention: The details of posted journals cannot be changed.Use trial balance reports to review account balances and activity in summary or detail. Determine which differences are errors requiring adjustment to the General Ledger. Other journal entry adjustments. Debtors Control. 16. * Reconcile Subsidiary Ledgers Identify differences between subsidiary ledgers and the General Ledger. etc. for example. write-offs (refer Accrual Write-Off Report). Creditors Control. With General Ledger Entry Reconciliation. Intercompany accounts. You can report on foreign currency. and descriptions and reference information for each journal entry line. Oracle Financials E-Business Suite Release 12 Period End Procedures 77 . * Check other key system accounts have not been transacted by ad-hoc journals. and manual accruals can be entered into Oracle General Ledger at this point also. 15. posted. Perform Final Adjustments Enter and Post any final adjustments as required by the organization. create and post adjusting and reversing journals. * Journal Reconciliation: General Ledger Entry Reconciliation lets you reconcile transactions in GL accounts that should balance to zero. for example. except to mark or unmark for reversal. Attention: If suspense accounting is not allowed.

Choose status „Open‟ to open a new accounting period. With a data access set across ledgers programs can be run for multiple ledgers from a single responsibility. FSGs can also be published via the Application Desktop Integrator (ADI). Oracle Payables. or „permanently closed‟. With a data access set across ledgers programs can be run for multiple ledgers from a single responsibility. This is controlled by GL: Data Access Set profile option. or to re-open a previously soft closed period to enable adjustments to be made. This operation can be performed across ledgers provided „Data Access Set‟ grants access.17. The Tax Reporting Ledger consists of accounting information created in Oracle Receivables. 20. including withholding tax. and Oracle General Ledger. Run Reports for Tax Reporting Purposes (Optional) A variety of standard reports can be used to provide tax information. Run final Financial Statement Generator Reports (FSG) or Report Sets as required by the organization including Income Statements and Balance Sheets. Run Financial Reports for the Closed Period Run a final Trial Balance Report. Close the Current Oracle General Ledger Period Close the current GL accounting period in the Open and Close Periods window. 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. The Financial Tax Register can be used to view the output from the Tax Reporting Ledger using Reports Exchange and Application Desktop Integrator (ADI). Open the Next Oracle General Ledger Period Open the next General Ledger accounting period in the Open and Close Periods window. which is required to be reported to the relevant Tax Authority. The period can be „soft closed‟. This step will need to be repeated for each ledger unless a data access set is setup to give access to multiple ledgers. The Financial Tax Register uses this data to generate Tax Register reports using the Rxi reporting tool. Using these products you can change the layout of the report. Generate and post reversal journals that were entered in the prior period. publish the report in different formats. For example any Oracle Purchasing receipted accruals and manual accruals. Any Journals entered into this period while it had a status of Future Enterable. and export the data to a tab delimited or HTML file. can now be posted as the period now has a status of Open. 18. The following tax registers are available: a) Deferred Output Tax Register b) Recoverable and Non-Recoverable Tax Registers Oracle Financials E-Business Suite Release 12 Period End Procedures 78 . 19. This is controlled by GL: Data Access Set profile option. For more information please refer to Oracle General Ledger User guide. if later adjustments to the balances for that period may be applicable.

Perform Encumbrance Year End Procedures (Optional) Oracle Financials provides a number of facilities for the processing of outstanding encumbrances as part of year-end processing. Other facilities available: * Use mass allocations to bring forward part of the funds available. or to a separate budget to identify between current year and carry forward amounts if required. you may also need to update the following: Define Budget Organizations. To perform Encumbrance year-end procedures.c) Single Cross Product Tax Register d) Standard Input and Output Tax Registers 21. b) Open the next budget year Use the Define Budget window to define a budget for the next budget period. Verify that the next year budget figures have been entered. and the encumbered budget. c) Run Year End Carry Forward Oracle Financials E-Business Suite Release 12 Period End Procedures 79 . * Carry forward the funds available as at the end of the year. where you have attached the funding budget to defined account ranges within this form. including Carry Forward. Attention: Ensure that the budget that you use is inclusive of the periods for the next budget year that you require Attention: Ensure that the calendar periods for the next budget year have been created prior to running this step. where summary templates are used as the basis for the budgetary control procedures. you must complete each of the following steps: a) Open the next encumbrance year Use the Open and Close Periods window to open the next encumbrance year. Define Summary Accounts. The default processing for Oracle Financials at year end is to extinguish any outstanding encumbrances/ unused funds when you close the last period of the Financial Year within the General Ledger application. * Carry forward budgets into the current appropriation budget. Mass budget processing also allows you to combine these budgets. If you define a new budget for the purposes of the next year budgetary control. * Carry forward encumbrances. The carry forward process enables managers to perform any of the following: * Carry forward encumbrances for existing transactions (purchases/requisitions).

Select the range of relevant accounting flexfields to be carried forward. Oracle Financials E-Business Suite Release 12 Period End Procedures 80 .Select „All‟ for all encumbrances. Commitment. Obligation etc. or Funds Available as the basis for the Carry forward * Encumbrance Type . Encumbrances and the Encumbered Budget.e.Select the budgets where they are different * Accounting Flexfield Ranges . or select the encumbrance type that you require i.This process enables you to determine the criteria that you want to use for carrying forward your encumbrances The year-end carry forward is normally completed in two steps: 1) Perform the Year End Carry Forward in Preview mode 2) Perform the Year End Carry Forward without selecting the Preview option Within the Year End Carry Forward form. you can select a wide range of criteria for carrying forward balances: * Carry Forward Rule .This rule enables you to select Encumbrances Only. * From/To Budget and Budget Organization.

Chapter 12 Period End Processing . Assets (Chapter 9) Treasury (Chapter 10) 1. Run the Payables Approval Process for All Invoices Receivables (Chapter 6) Purchasing (Chapter 7) 1. Review & Resolve Amounts to Post to the General Ledger 4. Reconcile Payments to Bank Statement Activity for the Period 5.Review Customer Acceptances (Optional) 5. Close the Current Oracle Payables Period 3. Generate Accruals and Amortization 4. Perform Revaluation 2. Review Open Orders and Check the Workflow Status 4. Generate Journals 5.Review Back Orders 1. to the General Ledger 6. Complete All Transactions for the Period Being Closed Cash Management (Chapter 3) 1. Transfer Journals to General Ledger 6. Complete All Transactions for the Period Being Closed 2. Follow Up Outstanding Invoices 5. Complete Daily Cash Management Activities Payables (Chapter 4) 1. 2. Transfer All Approved Invoices and Payments. Projects (Chapter 5) Order Management (Chapter 2) 1. Complete All Transactions for the Period Being Closed.Review and Correct Order Exceptions 81 . Complete All Maintenance Activities Oracle Financials Release 12 Period End Procedures 8. Check and fix pending Transactions. Complete All Transactions for the Period Being Closed 2. Review the Payables to General Ledger Posting Process After Completion 7.Review Discounts 7. Review the Outstanding and Overdue Purchase Orders (Optional) 4.Summary The following table displays a summary of the period-end procedures for each of the Financials applications detailed in the preceding chapters and. Review Held Orders 3. Submit the Unaccounted Transactions Sweep Program 8. an indication of the order in which the steps should be undertaken. Ensure all Interfaces are Completed for the Period (Optional) 3. Ensure the Next Accounting Period Status is Set to Future Entry 2. Check Inventory and Work In Process Transaction Interfaces. Review the Current and Future Commitments (Optional) 3. Complete the Oracle Payables Period End Process 7. Change the Current Oracle Projects Period Status from Open to Pending Close 2. Identify and Review Un-invoiced Receipts (Period-End Accruals) 6. Complete Daily Trading Activities General Ledger (Chapter 11) 1. Follow up ReceiptsCheck with Suppliers Inventory / Cost Management (Chapter 8) 1. Open the Next Oracle Projects Period 3. 3.

Open the Next Inventory Period 6. Reconcile to Inventory 10. Create Service Contracts (Optional) 4.Generate Draft Revenue for All Projects 9.Run Create Accounting 12. Load Bank Statements 3.Projects (Chapter 5) 4.Review and Release Revenue for All Projects 10.Run the Generate Cost Accounting Events Program 7.Interface Transactions to Other Applications Order Management (Chapter 2) Cash Management (Chapter 3) Payables (Chapter 4) Receivables (Chapter 6) Purchasing (Chapter 7) Inventory / Cost Management (Chapter 8) Assets (Chapter 9) Treasury (Chapter 10) General Ledger (Chapter 11) 2. Accrue Un-invoiced Receipts 1. 5. Review AutoReconciliation Execution Report 9. Run Maintenance Processes 5. Reconcile receipts. Reconcile Accounts .Perpetual Accruals 10. Reconcile Outstanding Customer Balances 4. Reconcile Oracle Payables Activity for the Period 11. Review the Unapplied Receipts Register 5. Run the Cost Distribution Processes 6a.Generate Invoices 5. Transfer Summary or Detail Transactions 9. Run Receipt Accruals . Perform Year End Encumbrance Processing. Complete All Transactions for the Period Being Closed 2.Run Generation Revenue Accounting Events Process 11. Run Calculate Gains and Losses (Optional) Oracle Financials E-Business Suite Release 12 Period End Procedures 82 . Run Mass Additions Transfer to Oracle Assets 9. Create Miscellaneous Transactions 6a. Complete All Transactions for the Period Being Closed 2. Complete Bank Transfers 7. Close the Current Oracle Payables and Oracle Purchasing Periods 1. Complete All Transactions for the Period Being Closed 6. Assign All Assets to Distribution Lines 3. 8. (Optional) 11. Generate Sweep Transactions 4. Reconcile Bank Statements 6. Generate Bank Statement Cash flows 8.Period End Process 10. Close the Current Oracle Purchasing Period. Reconcile Transaction Activity for the Period 3.

Projects (Chapter 5) Order Management (Chapter 2) 11.Advance the PA Reporting Period (optional) 18. Reconcile Posted Journal Entries Oracle Financials E-Business Suite Release 12 Period End Procedures 83 . Open the Next Oracle Payables Period 12. Post to the General Ledger Purchasing (Chapter 7) Inventory / Cost Management (Chapter 8) 7.Restore Access to User Maintenance Activities 20. Run the GL Reconciliation Report 9. 11. Reconcile Cost Distribution Lines with General Ledger (Optional) 21. 8. Permanently Close the Oracle Projects Period (Optional) 14.Update Project Summary Amounts 10. Run the Account Analysis Report for the General Ledger Cash Account 15. Rollback Depreciation 15. Run Standard Period End Reports Cash Management (Chapter 3) Payables (Chapter 4) Receivables (Chapter 6) 6. Resolve Exceptions on the Auto Reconciliation Execution Report 9. Validate the Work in Process Inventory 5. Run Final Project Costing and Revenue Management Reports 16.Run Period Close Exceptions and Tieback Reports 8. Review the Subledger Period Close Exceptions Report 13. Create Deferred Depreciation Journal Entries (Optional) 8. Review and Post Journal Entries 10. Complete NonOracle Sub-ledger Interfaces to Oracle General Ledger (Optional) 19. Reconcile to Oracle Receivables (Optional) 12. Resolve Unreconciled Statement Lines 9. Create Accounting 8. Correct any Invalid Entries to the General Ledger Cash Account (Optional) 14. Run Standard Period End Reports (Optional) 7. Run Standard Period End Reports and reconcile the Perpetual Inventory with GL 9. Run Depreciation Treasury (Chapter 10) General Ledger (Chapter 11) 13. Close the Current Inventory Period Assets (Chapter 9) 4. Run Transactions Available for Reconciliation Report 11. Run Bank Statement Detail Report 12. Close the Current Oracle Receivables Period 12. Reconcile Receipts to Bank Statement Activity for the Period 7. Run Responsibility Reports (Optional) 11. Third Party Balances Report 2. Open the Next Oracle Purchasing Period. Depreciation Projections (Optional) 12. Upload Journals from ADI (Applications Desktop Integrator) to Oracle General Ledger (optional) 4. Reconcile Oracle Assets to Oracle General Ledger Using Reports.Transfer Invoices to Oracle Receivables 14. Print Invoices 13.Change the Current Oracle Projects Period Status from Pending Close to Closed 17. Post to General Ledger 13. Reconcile the General Ledger Transfer Process 6. Reconcile the Journal Import Process 10. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger 3. Review the Account Analysis Report 16.

Post All Journal Batches 9a. Run GL Trial Balances and Preliminary Financial Statement Generator Reports (FSGs) 11. Run the Key Indicators Report (Optional) Receivables (Chapter 6) 15. Generate Reversal Journals (Optional) 6. Reconcile Intercompany (optional) 14. Run Reports for Tax Reporting Purposes (Optional) 14. Consolidate Ledgers (Optional) 13a. Review and Verify Journal Details of Unposted Journal Entries 9. Translate Balances (Optional) 13. Run the Period Close Exceptions Report 10. Generate Recurring Journals (Optional) 7. Close the Current Oracle General Ledger Period Oracle Financials E-Business Suite Release 12 Period End Procedures 84 . Run Reports for Tax Reporting Purposes (Optional) Purchasing (Chapter 7) Inventory / Cost Management (Chapter 8) Assets (Chapter 9) Treasury (Chapter 10) General Ledger (Chapter 11) 5. Perform Final Adjustments 17. Enter Adjustments and / or Accruals and Post 16. Review Account Analysis Report 17. Review and Correct Balances (Perform Reconciliations) 15.Projects (Chapter 5) Order Management (Chapter 2) Cash Management (Chapter 3) Payables (Chapter 4) 13. Review the Unposted Items Report 16. Generate Mass Allocation Journals (Optional) 8. Revalue Balances (Optional) 12. Open the Next Oracle Receivables Period 18.

Run Reports for Tax Reporting Purposes (Optional) 21. Run Financial Reports for the Closed Period 20. Open the Next Oracle General Ledger Period 19. Perform Encumbrance Year End Procedures (Optional) Oracle Financials E-Business Suite Release 12 Period End Procedures 85 .Projects (Chapter 5) Order Management (Chapter 2) Cash Management (Chapter 3) Payables (Chapter 4) Receivables (Chapter 6) Purchasing (Chapter 7) Inventory / Cost Management (Chapter 8) Assets (Chapter 9) Treasury (Chapter 10) General Ledger (Chapter 11) 18.

.

1 558421.aka Open Account AP Balances Listing R12 Trial Balance FAQs R12 Troubleshooting Accounting Issues (in Payables) R12 Troubleshooting Period Close in Payables R12: Oracle Financials Year-End Close and Reconciliation Resources R12: The Differences between the AP Trial Balance in R12 and 11i Release 12 Close Process & Reconciliation .1 735522.0. Key: R12) November 19 SLA: Troubleshooting the AP TO GL Reconciliation Subledger Accounting (SLA): FAQ for Support Engineers 749679.1 604739.1 579836.1 751830. Document Title Doc ID AR: What are the recommended patches for AR-GL Posting.1 732928. Period Close and Trial Balance 'How To' documents R12 SLA: New R12 Payables Trial Balance -.4 Reconciliation Reports On Standard Cash Receipt.1 437422.1 579373. Reconciliation and Data Integrity Issues? 'FAQs' for Period Close and Unaccounted Transactions topic in Oracle Payables GL_DATE Difference On R12.1 What Is The Period Close Process For Oracle Assets In 557948.1 759002.Appendix: More Information Related My Oracle Support Information The following My Oracle Support Information can be reviewed for additional information on period end procedures.1 Useful Articles for R12 General Ledger Support Engineers 369993.1 740297.1 436128.1 Release 12? Oracle Financials Release 12 Period End Procedures 87 .7:00 pm MDT (Conf. How To Diagnose And Reconcile R12 Inventory AP Accrual Transactions Using Reconciliation Reports How To Diagnose Issues With Create Accounting Process For Procure To Pay Cycle in R12 Period Close Reconciliation Report Is Showing Unusual Discrepancy R12 Accounting FAQ's R12 Accounting.1 605707.1 728871.1 743390. GL Transfer.1 579631.1 761502.

without our prior written permission. Mien-Lin Tan. Amrita Mehrok. Elise Mattei. Sarah Bowen. This document is provided for information purposes only and the contents hereof are subject to change without notice. Menno Koomen. Kannan Tarakad. whether expressed orally or implied in law. Chris Cianciolo. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Henk Brons Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. Julia Baeva. Ramaswamy Krishnamurti.com Copyright © 2009. Simer Sahani. Lucia Scaltriti.650. Helle Hennings. Ashish Pathak. Barbara Fox. This document may not be reproduced or transmitted in any form or by any means.Change Log Jun 2009 16-Aug-2010 Published White Paper Updated the column headings for the table in Chapter 12 Oracle Financials Release 12 Period End Procedures June 2009 Author: Oracle Consulting Contributing Authors and Reviewers: Suneel Bhaskar.S. Oracle Financials Release 12 Period End Procedures 88 . including implied warranties and conditions of merchantability or fitness for a particular purpose. This document is not warranted to be error-free. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.506.A.7000 Fax: +1. Worldwide Inquiries: Phone: +1. Bill Tokheim. Other names may be trademarks of their respective owners.650. nor subject to any other warranties or conditions. CA 94065 U. for any purpose. Terrance Wampler. Bertrand Vuigner. electronic or mechanical. Murali Voora.7200 oracle.506. Oracle and/or its affiliates. All rights reserved.

Sign up to vote on this title
UsefulNot useful