P. 1
EBS_period_end_close_R12

EBS_period_end_close_R12

|Views: 244|Likes:
Published by Bhaumik Jambusaria

More info:

Published by: Bhaumik Jambusaria on Feb 04, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

11/14/2011

pdf

text

original

Sections

  • Chapter 1 SLA and Period End Close dependencies
  • Sub Ledger Accounting (SLA) – Business Process
  • Sub Ledger Accounting (SLA) – Process Change
  • Subledger Accounting (SLA) – Reconciliation
  • Subledger Accounting (SLA) Close Process – General Steps
  • General – Period End Close Dependencies
  • Chapter 2 Oracle Projects
  • Business Requirements
  • Project Periods and General Ledger Periods
  • Period Statuses
  • General Exception Handling at Period End
  • Procedures
  • 2. Open the Next Oracle Projects Period
  • 3. Complete all Maintenance Activities
  • 4. Run Maintenance Processes
  • 5. Complete All Transactions for the Period Being Closed
  • 6. Run the Cost Distribution Processes
  • 6a. Run the Generate Cost Accounting Events Program
  • 7. Interface Cost Transactions to Other Applications
  • 8. Generate Draft Revenue for All Projects
  • 9. Review and Release Revenue for All Projects
  • 10. Run Generation Revenue Accounting Events Process
  • 11. Run Create Accounting to Process Revenue Accounting Events
  • 12. Generate Invoices
  • 13. Transfer Invoices to Oracle Receivables
  • 14. Run Period Close Exceptions and Tieback Reports
  • 15. Run Final Project Costing and Revenue Management Reports
  • 17. Advance the PA Reporting Period (Optional)
  • 18. Update Project Summary Amounts
  • 19. Restore Access to User Maintenance Activities
  • 20. Reconcile Cost Distribution Lines with General Ledger (Optional)
  • 21. Permanently Close the Oracle Projects Period (Optional)
  • Chapter 3 Oracle Order Management
  • 1. Complete All Transactions for the Period Being Closed
  • 2. Ensure all Interfaces are Completed for the Period (Optional)
  • 3. Review Open Orders and Check the Workflow Status
  • 4. Review Held Orders
  • 5. Review Customer Acceptances (Optional)
  • 6. Review Discounts
  • 7. Review Backorders
  • 8. Review and Correct Order Exceptions
  • 9. Reconcile to Oracle Inventory
  • 10. Create Service Contracts (Optional)
  • 11. Reconcile to Oracle Receivables (Optional)
  • 12. Run Standard Period End Reports
  • Chapter 4 Oracle Cash Management
  • 1. Complete Daily Cash Management Activities
  • 2. Load Bank Statements
  • 3. Generate Sweep Transactions
  • 4. Create Bank Statement Cashflows
  • 5. Reconcile Bank Statements
  • 6. Create Miscellaneous Transactions
  • 6a.Complete Bank Transfers
  • 7. Review Auto-Reconciliation Execution Report
  • 8. Resolve Exceptions on the Auto-Reconciliation Execution Report
  • 9. Run Bank Statement Detail Report
  • 10. Run Transactions Available for Reconciliation Report
  • 11. Resolve Un-reconciled Statement Lines
  • 12. Post to General Ledger
  • 13. Run the GL Reconciliation Report
  • 14. Run the Account Analysis Report for the General Ledger Cash Account
  • 15. Review the Account Analysis Report
  • Chapter 5 Oracle Payables
  • 2. Run the Payables Approval Process for All Invoices
  • 3. Review and Resolve Amounts to Post to the General Ledger
  • 4. Reconcile Payments to Bank Statement Activity for the Period
  • 5. Transfer All Approved Invoices and Payments to the General Ledger
  • 7. Submit the Unaccounted Transactions Sweep Program
  • 8. Close the Current Oracle Payables Period
  • 9. Accrue Uninvoiced Receipts
  • 10. Reconcile Oracle Payables Activity for the Period
  • 11. Run Mass Additions Transfer to Oracle Assets
  • 12. Open the Next Oracle Payables Period
  • 13. Run Reports for Tax Reporting Purposes (Optional)
  • 14. Run the Key Indicators Report (Optional)
  • 15. Purge Transactions (Optional)
  • Chapter 6 Oracle Receivables
  • 2. Reconcile Transaction Activity for the Period
  • 3. Reconcile Outstanding Customer Balances
  • 4. Review the Unapplied Receipts Register
  • 5. Reconcile Receipts
  • 6. Reconcile Receipts to Bank Statement Activity for the Period
  • 7. Post to the General Ledger
  • 8. Reconcile the General Ledger Transfer Process
  • 9. Reconcile the Journal Import Process
  • 10. Print Invoices
  • 11. Close the Current Oracle Receivables Period
  • 12. Review the Subledger Period Close Exceptions Report
  • 13. Third Party Balances Report
  • 14. Reconcile Posted Journal Entries
  • 15. Review the Unposted Items Report
  • 16. Review Account Analysis Report
  • 17. Open the Next Oracle Receivables Period
  • 18. Run Reports for Tax Reporting Purposes (Optional)
  • 19. Run Archive and Purge Programs (Optional)
  • Chapter 7 Oracle Purchasing
  • 2. Review the Current and Future Commitments (Optional)
  • 3. Review the Outstanding and Overdue Purchase Orders (Optional)
  • 4. Follow Up Receipts - Check With Suppliers
  • 5. Identify and Review Un-invoiced Receipts (Period-End Accruals)
  • 6. Follow Up Outstanding Invoices
  • 7. Complete the Oracle Payables Period-End Process
  • 8. Run the Receipt Accruals - Period End Process
  • 9. Reconcile Accrual Accounts - Perpetual Accruals
  • 10. Perform Year End Encumbrance Processing (Optional)
  • 11. Close the Current Oracle Purchasing Period
  • 12. Open the Next Oracle Purchasing Period
  • 13. Run Standard Period End Reports (Optional)
  • Chapter 8 Oracle Inventory-Cost Management
  • 3. Check and fix pending Transactions
  • 4. Transfer Summary or Detail Transactions
  • 5. Open the Next Inventory Period
  • 6. Close the current Oracle Payables and Oracle Purchasing Periods
  • 7. Close the Current Inventory Period
  • 9. Validate the Work in Process Inventory
  • Chapter 9 Oracle Assets
  • 2. Assign All Assets to Distribution Lines
  • 3. Run Calculate Gains and Losses (Optional)
  • 4. Run Depreciation
  • 5. Create Accounting
  • 6. Rollback Depreciation
  • 7. Create Deferred Depreciation Journal Entries (Optional)
  • 8. Depreciation Projections (Optional)
  • 9. Review and Post Journal Entries
  • 10. Reconcile Oracle Assets to the General Ledger Using Reports
  • 11. Run Responsibility Reports (Optional)
  • 12. Archive and Purge Transactions (Optional)
  • Chapter 10 Oracle Treasury
  • 1. Complete Daily Trading Activities
  • 2. Perform Revaluation
  • 3. Generate Accruals and Amortization
  • 4. Generate Journals
  • 5. Transfer Journals to General Ledger
  • Chapter 11 Oracle General Ledger
  • Period End Close
  • Combined Basis Accounting
  • 1. Ensure the Next Accounting Period Status is set to Future Entry
  • 2. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger
  • 5. Generate Reversal Journals (Optional)
  • 6. Generate Recurring Journals (Optional)
  • 7. Generate Mass Allocation Journals (Optional)
  • 8. Review and Verify Journal Details of Unposted Journal Entries
  • 9. Post All Journal Batches
  • 9a. Run the Period Close Exceptions Report
  • 11. Revalue Balances (Optional)
  • 12. Translate Balances (Optional)
  • 13a. Reconcile Intercompany (optional)
  • 14. Review and Correct Balances (Perform Reconciliations)
  • 15. Enter Adjustments and / or Accruals and Post
  • 16. Perform Final Adjustments
  • 17. Close the Current Oracle General Ledger Period
  • 18. Open the Next Oracle General Ledger Period
  • 19. Run Financial Reports for the Closed Period
  • 20. Run Reports for Tax Reporting Purposes (Optional)
  • 21. Perform Encumbrance Year End Procedures (Optional)
  • Chapter 12 Period End Processing - Summary
  • Appendix: More Information
  • Related Metalink Information

ORACLE FINANCIALS E-BUSINESS SUITE, RELEASE 12

PERIOD-END PROCEDURES An Oracle White Paper April, 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. The contributing authors and reviewers can be found on the last page. If you have any comments or feedback, please read the paragraph ‘Status and Feedback’ below.

Objectives
This document outlines the 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 yearend 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 Metalink 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

CHAPTER 2 ORACLE PROJECTS.............................................................................................................................................12

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 Business Requirements..................................................................................12

Procedures.....................................................................................................13

Project Periods and General Ledger Periods....................................................12 Period Statuses................................................................................................12 General Exception Handling at Period End......................................................12 1. Change the Current Oracle Projects Period Status from Open to Pending Close................................................................................................................13 2. Open the Next Oracle Projects Period.........................................................13 3. Complete all Maintenance Activities ..........................................................13 4. Run Maintenance Processes ......................................................................14 5. Complete All Transactions for the Period Being Closed..............................14 6. Run the Cost Distribution Processes............................................................15 6a. Run the Generate Cost Accounting Events Program ...............................16 7. Interface Cost Transactions to Other Applications......................................16 8. Generate Draft Revenue for All Projects.....................................................16 9. Review and Release Revenue for All Projects.............................................16 10. Run Generation Revenue Accounting Events Process...............................17 11. Run Create Accounting to Process Revenue Accounting Events...............17 12. Generate Invoices......................................................................................17 13. Transfer Invoices to Oracle Receivables....................................................17 14. Run Period Close Exceptions and Tieback Reports...................................17 15. Run Final Project Costing and Revenue Management Reports.................18 16. Change the Current Oracle Projects Period Status from Pending Close to Closed..............................................................................................................18 17. Advance the PA Reporting Period (Optional).............................................18 18. Update Project Summary Amounts...........................................................18 19. Restore Access to User Maintenance Activities.........................................19 20. Reconcile Cost Distribution Lines with General Ledger (Optional)............19 21. Permanently Close the Oracle Projects Period (Optional).........................19

CHAPTER 3 ORACLE ORDER MANAGEMENT.............................................................................................................................20

Business Requirements..................................................................................20 Procedures.....................................................................................................20
1. 2. 3. 4. 5. 6.

Complete All Transactions for the Period Being Closed..............................20 Ensure all Interfaces are Completed for the Period (Optional)....................21 Review Open Orders and Check the Workflow Status.................................22 Review Held Orders.....................................................................................22 Review Customer Acceptances (Optional)..................................................23 Review Discounts........................................................................................23

Oracle Financials E-Business Suite Release 12 Period End Procedures

.........24 9......................................26 2...............................................................................................33 8............................................ Reconcile Oracle Payables Activity for the Period.... Reconcile Payments to Bank Statement Activity for the Period.......................................................................................................................................................30 CHAPTER 6 ORACLE RECEIVABLES............... Accrue Uninvoiced Receipts.................Complete Bank Transfers.... 2.......................28 13.................................. Post to General Ledger.................. ..............39 Reconcile Transaction Activity for the Period.......................... Run the Key Indicators Report (Optional).... Close the Current Oracle Payables Period.............................27 6............................................................................ Review the Account Analysis Report..........................................39 1..27 8....................24 10.....................................................................................................................................................................................................28 9....... Run Bank Statement Detail Report............................................26 4.......................................... Create Miscellaneous Transactions...........................36 14....... Correct any Invalid Entries to the General Ledger Cash Account (Optional) ................ Complete All Transactions for the Period Being Closed....................................................................... Run Standard Period End Reports................................... Review and Resolve Amounts to Post to the General Ledger......... Generate Sweep Transactions........34 9................................... 3....................................... Reconcile to Oracle Inventory ..........................39 Reconcile Outstanding Customer Balances..........29 16................................................................................. Review the Payables to General Ledger Posting process After Completion........38 Business Requirements..........................26 7............................................................36 12............... Submit the Unaccounted Transactions Sweep Program............. Load Bank Statements............................................... Transfer All Approved Invoices and Payments to the General Ledger.........................42 Reconcile Receipts.........................27 5..................................... Run the GL Reconciliation Report..............32 6...............28 12.......................................................................28 11..................................32 5...............................................................31 3.................................................................... Review Backorders.........27 6a.............................30 2..34 11...........................................................................................24 11............... Review Auto-Reconciliation Execution Report.........37 15............................. Create Service Contracts (Optional) ..................... Run the Payables Approval Process for All Invoices......... Create Bank Statement Cashflows....................29 CHAPTER 5 ORACLE PAYABLES.....................................29 15...............................................28 10.................................................... 4..................30 Procedures.......................... Resolve Exceptions on the Auto-Reconciliation Execution Report....................................26 1................26 Procedures........................24 12......................................................................................................................... Resolve Un-reconciled Statement Lines............42 Oracle Financials E-Business Suite Release 12 Period End Procedures ........................................................................................31 4...................................... Complete All Transactions for the Period Being Closed...................................................................... Purge Transactions (Optional)..................................39 Procedures.....CHAPTER 4 ORACLE CASH MANAGEMENT ........... ......................... Run Transactions Available for Reconciliation Report.................................. Run Mass Additions Transfer to Oracle Assets..........................................................23 8.........................41 Review the Unapplied Receipts Register..........29 14......30 Business Requirements....................................36 13..........33 7............39 1............................................................................................... Open the Next Oracle Payables Period................. Run the Account Analysis Report for the General Ledger Cash Account......................25 Business Requirements........... Reconcile Bank Statements................. Review and Correct Order Exceptions............ Reconcile to Oracle Receivables (Optional) ................................ Complete Daily Cash Management Activities......................................................................34 10........27 7...26 3........... 5.......................................... Run Reports for Tax Reporting Purposes (Optional).............................

............................................ Validate the Work in Process Inventory......... Run Reports for Tax Reporting Purposes (Optional)...53 CHAPTER 8 ORACLE INVENTORY-COST MANAGEMENT..............................................64 Oracle Financials E-Business Suite Release 12 Period End Procedures ....................................52 11....60 9.................57 CHAPTER 9 ORACLE ASSETS .................................Perpetual Accruals................62 Assign All Assets to Distribution Lines......... Close the Current Inventory Period................................................................................................. Run Archive and Purge Programs (Optional)... Reconcile Accrual Accounts ..................................... Review the Current and Future Commitments (Optional).......................47 3............47 Procedures............................. Review the Unposted Items Report...58 4..............53 13....45 19..............63 Create Accounting................................................................................................................................................................. Complete All Transactions for the Period Being Closed................................44 10.............................................................................. Run Standard Period-End Reports and reconcile the Perpetual Inventory with GL............................ Close the Current Oracle Purchasing Period.........58 3...............................................................................................................................................43 7................ Close the current Oracle Payables and Oracle Purchasing Periods.............................. Close the Current Oracle Receivables Period............49 10.... Follow Up Outstanding Invoices....... Run Standard Period End Reports (Optional)..................................48 9..................45 18...................................................................... Reconcile Receipts to Bank Statement Activity for the Period...................................................................................... 3........64 Create Deferred Depreciation Journal Entries (Optional)........64 Depreciation Projections (Optional)...............................47 4........ Post to the General Ledger.................................. Third Party Balances Report.................................62 Procedures........................... Open the Next Inventory Period...........57 Business Requirements.......................................................................... Complete All Transactions for the Period Being Closed.44 12... Transfer Summary or Detail Transactions ....................... 8... Review the Subledger Period Close Exceptions Report......................................................................... Identify and Review Un-invoiced Receipts (Period-End Accruals)..... Reconcile the Journal Import Process.........53 12....................................... Check Inventory and Work in Process Transaction Interfaces............. 6....................45 16...........................44 11.....48 6.......47 6.....45 14........................CHAPTER 7 ORACLE PURCHASING.................................................................43 8........................45 17...................................... Complete All Transactions for the Period Being Closed.... 7.................................................................................................Period End Process.......... Reconcile the General Ledger Transfer Process..................................... Perform Year End Encumbrance Processing (Optional)........................57 2.................................................................. Check and fix pending Transactions ..........62 1................................................................................ Review Account Analysis Report...........................................48 7...........................................59 7.......62 1.....62 Run Depreciation........................59 8...............................................................46 Business Requirements..............................45 15.....................................................................48 8.47 1..................................... Review the Outstanding and Overdue Purchase Orders (Optional).................... 5....... Open the Next Oracle Receivables Period....................Check With Suppliers....................................................... Open the Next Oracle Purchasing Period............................................................................................................ 2.......................... Run the Receipt Accruals .................................................................. Reconcile Posted Journal Entries ....58 5..................................................................................................57 Procedures............................. Print Invoices........61 Business Requirements........ Complete the Oracle Payables Period-End Process.......................59 6.......................................43 9......... Follow Up Receipts ....48 5..................................................62 Run Calculate Gains and Losses (Optional)..........63 Rollback Depreciation ................44 13........... 4..............................47 2.........................................................................

............................77 16........... Archive and Purge Transactions (Optional)..........74 13. Upload Journals from ADI (Applications Desktop Integrator) to Oracle General Ledger (Optional)...68 9........................................................................................................................77 19................................................74 11....70 1....70 Business Requirements....... Review and Post Journal Entries.... 4.................. Consolidate Ledgers (Optional)....72 9......... Run Responsibility Reports (Optional).........................71 3........78 20...................................................................................................66 Business Requirements.............................................................................................................69 Transfer Journals to General Ledger.......... Reconcile Oracle Assets to the General Ledger Using Reports................72 6.......................................................................... 2............68 Generate Accruals and Amortization.... Run Financial Reports for the Closed Period.............................74 10.......................................SUMMARY ............74 13a................ Run Reports for Tax Reporting Purposes (Optional)............................................................80 APPENDIX: MORE INFORMATION ........................................................................................................................................................................................................CHAPTER 10 ORACLE TREASURY .................................................................78 CHAPTER 12 PERIOD END PROCESSING ................. Run GL Trial Balances and Preliminary Financial Statement Generator Reports (FSGs)...............70 Procedures.......................72 8..................................................................................................................................................................................... Open the Next Oracle General Ledger Period................ Run the Period Close Exceptions Report...........................................72 7...... Reconcile Intercompany (optional).... Complete Oracle Sub-ledger Interfaces to Oracle General Ledger..........................................68 Procedures..................66 12.................................................................. Complete Daily Trading Activities.............71 4.........................................................................................64 10............................................................... Review and Verify Journal Details of Unposted Journal Entries.73 9a................ Perform Encumbrance Year End Procedures (Optional)...........................69 CHAPTER 11 ORACLE GENERAL LEDGER........................................71 2................................ Translate Balances (Optional)..................................................... Generate Reversal Journals (Optional).................... Perform Final Adjustments.......... Generate Mass Allocation Journals (Optional)......68 1..............74 12........ 3....................................................................................................65 11............................................................................................................... Enter Adjustments and / or Accruals and Post ....78 21...................................................................77 18................... Complete Non-Oracle Sub-ledger Interfaces to Oracle General Ledger (Optional: only required if you want to post from non-Oracle systems).85 Oracle Financials E-Business Suite Release 12 Period End Procedures ................................................. Generate Recurring Journals (Optional)..........................................................68 Generate Journals........85 Related Metalink Information........................... Ensure the Next Accounting Period Status is set to Future Entry...............77 17.................. Post All Journal Batches............................................. Revalue Balances (Optional).... Review and Correct Balances (Perform Reconciliations).................................................................................................................68 Perform Revaluation.............................................72 5...................................... 5.........76 14..........................76 15...................................70 Combined Basis Accounting................................. Close the Current Oracle General Ledger Period..............................70 Period End Close..........................................................................

• It allows your general ledger to be free of extraneous data. and for ease of drilldown. 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. It behaves like a detailed version of your general ledger and provides a rich store of information for reporting and analysis. • Just as Oracle General Ledger stores balances and journals. Subledger Accounting offers a new model between the subledgers and GL. 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. the accounting is generated by Subledger Accounting. for internal and external audit purposes. Whenever you want to account for your subledger transactions. Subledger Accounting helps to maintain a common link between General Ledger balances and underlying transactions automatically. online or as a background batch process.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. Subledger Accounting provides a comprehensive view of all subledger accounting data. • The moment you need to access more detailed information. 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.

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

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

you close all of your subledgers before you close General Ledger. Oracle Financials E-Business Suite Release 12 Period End Procedures 11 .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. You also need to close Oracle Payables before you close Oracle Inventory and Oracle Assets. The diagram above shows the dependencies between some of the main Financials products and a couple of supply chain products. as bank reconciliation in Cash Management will create miscellaneous receipts in Oracle Receivables. You actually have to close Oracle Cash Management before you close Oracle Receivables. You have to close Oracle Payables before you close Oracle Purchasing to account for purchasing accruals at period end. Finally.

transactions are summarized into periodic cycles for reporting and reconciliation.Chapter 2 Oracle Projects This chapter describes the procedures for performing period-end processing in Oracle Projects Release 12. Suggestion: If you have different periods in Projects. Project periods may be based on a different period of time such as a week.Period has never been used. This will enable you to more easily align Projects with General Ledger for reconciliation purposes.Period is closed for processing. such as Projects. If the two sets of periods overlap. projects may be based on a different periodic cycle to that of the general ledger. Most subledgers have a periodic cycle that parallels the general ledger fiscal cycle.This status prevents transaction entry. 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. Period Statuses Oracle Projects has statuses similar to the standard period statuses as in other modules: *Never Opened .No further processing is possible. * Permanently Closed . * Closed . while allowing minimum interruption of transaction processing.Period is open to accept transactions from other modules. but can be re-opened if required. you may want to consider using one of the alternate general ledger period conventions. such as a 5-4-4 period split. and allows users to correct unprocessed items prior to completing the period close. * Future Enterable .Period is available for data entry. * Pending Close . and transactions are likely to be posted across modules. Project Periods and General Ledger Periods In Oracle subledgers. * Open . General Exception Handling at Period End If you do not want to correct exceptions during the current GL period. However. then you can run the process “PRC: Sweep Transaction Accounting Events” to change the Oracle Financials E-Business Suite Release 12 Period End Procedures 12 . then you may need to put in place special procedures for the reconciliation of Projects to the general ledger. and other modules. Usually used where modules are maintained in different periods.

Procedures 1. This process needs to be performed for each operating unit defined. 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. 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. Change the Current Oracle Projects Period Status from Open to Pending Close This is an interim status. which allows you to interface and adjust transactions in the period but does not allow transaction entry. 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 * Labor cost rates * Standard costing burden schedule maintenance Oracle Financials E-Business Suite Release 12 Period End Procedures 13 .date on unaccounted transaction accounting events to the first day of the next open GL period. Complete all Maintenance Activities As there are a number of maintenance activities that can affect the period close procedure. The Subledger Period Close Exceptions Report lists all accounting events and journal entries that fail period close validation. without accounting for them. START HERE 3. This process needs to be performed for each operating unit defined. 2.

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. 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. the period close. Transaction Source = Oracle Self-Service Time. Run PRC: Transaction Import. 4. Oracle Financials E-Business Suite Release 12 Period End Procedures 14 . import all eligible supplier invoices from Oracle Payables. 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. Run PRC: Compile All Burden Schedule Revisions b) Run organization maintenance to ensure all organizations have been added to all affected compiled burden schedules. or use function and responsibility restrictions to prevent access to these areas during the period close procedure. Run PRC: Add New Organization Compiled Burden Multipliers c) If changes or additions were made to pre-existing resource lists. Run the AUD: Missing Timecards Report Interface Supplier Invoices from Oracle Payables Before generating project revenue or running final cost event processes. If Oracle Projects is the direct data source for payroll or for reconciling labor costs to payroll. d) Run PRC: Update Project Summary Amounts After Resource List Change 5. update the project summary amounts before. Verify that all pre-approved timesheet batches in the current PA period have been released and approved. not during. verify that all timecards are entered or accounted for.

after verifying that all transactions for the period have been accounted for. ensure that all new supplier invoices processing for the current GL period has stopped. import all eligible expense reports from Oracle Payables to create pre-approved expense report batches. 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 * 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. 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. These expense reports may have been entered via Self-Service Expenses or Expense Reports in Oracle Payables. 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. Run PRC: Interface Supplier Invoices from Payables Interface Expense Reports from Oracle Payables Before generating project revenue or running final cost distribution processes.Warning: If your PA period matches a GL/AP month end. The following transaction sources are pre-defined. 6. Oracle Financials E-Business Suite Release 12 Period End Procedures 15 . Access to these activities should be controlled.

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

Run PRC: Generate Inter-Company Invoices for a Range of Projects for all projects. If it is transferred unposted. * Creates inter-company credit memos and invoice cancellations. the General Ledger posting program needs to be submitted. 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 14. Run Create Accounting to Process Revenue Accounting Events This program is owned by SLA and is used to generate accounting and then transfer it to the General Ledger based on appropriate parameters. These events will be used subsequently by the Create Accounting process to generate accounting. 13. The same is achieved by PRC: Create Accounting 12. * Deletes unreleased inter-company invoices. Run Generation Revenue Accounting Events Process Run PRC: Generate Revenue Accounting Events to generate events for revenue.10. Run Period Close Exceptions and Tieback Reports Run the period close exceptions reports to identify transactions that have not been fully processed. Attention: Interface processes have become obsolete. This process: * Creates inter-company invoices from cross–charged transactions previously identified by inter-company billing to be processed for cross charging. Generate Invoices Run PRC: Generate Invoices to generate invoices to be interfaced to Oracle Receivables. 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 Oracle Financials E-Business Suite Release 12 Period End Procedures 17 . 11. 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.

All the streamline options are not available in R12. Cost. Cost. Please refer to the user guide. Suggestion: Some of the above reports and processes may be run using the Submit Streamline Processes process. Budgets by Work Breakdown Structure * MGT: Employee Activity Report * MGT: Invoice Review * MGT: Unbilled Receivables Aging * MGT: Agreement Status by Customer 16. Run Final Project Costing and Revenue Management Reports Run all of the following project costing management reports: * MGT: Revenue. Budgets by Resources * MGT: Revenue. advance the PA Reporting Period. run the reports again until there are no exceptions. the change of status is not allowed. 15.* 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. the system checks to see if any unprocessed items exist in the period. Re-run the period close exception reports to identify any unprocessed items.Revenue. or completed more succinctly. 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. Some of them have become obsolete. This process needs to be performed for each operating unit defined. Change the Current Oracle Projects Period Status from Pending Close to Closed When changing the status to Closed. If you use the Streamline process. 17. Review these reports and make all the indicated corrections. 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. Only one period can be designated as the current reporting period for Project Status Inquiry. Oracle Financials E-Business Suite Release 12 Period End Procedures 18 . This process ensures processes and reports are run and completed in the correct order. If unprocessed items exist. 18. Attention: The update process cannot run concurrently with the interface processes. The current reporting period does not have to be an open period. After the corrections are made. Cost Budgets by Resources (Project Level) * MGT: Task . the order of some of the above steps may be changed.

current reporting period. 20. restore access to user maintenance activities. change the status of the PA period to Permanently Closed. 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.Warning: Do not run PRC: Update Project Summary Amounts After Resource List Change during the closing or post-closing processes. Oracle Financials E-Business Suite Release 12 Period End Procedures 19 . 19. Warning: Once a period is permanently closed it can never be re-opened. Restore Access to User Maintenance Activities After the project summary amounts have been updated for the closed. 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.

Closed orders are excluded from many of the standard reports available in Order Management. Business Requirements Open Sales Orders should be reviewed and. where possible. Procedures The following steps are taken in performing period-end processing for Oracle Order Management. Once an order is closed. 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. respectively.Chapter 3 Oracle Order Management This chapter describes the procedures for performing period-end processing in Oracle Order Management Release 12. increasing system speed and efficiency. * Close lines and close orders are implemented using workflow. confirm that service contracts for warranties and extended warranties have been created Close orders * Closing orders that are complete enhances performance. Oracle Financials E-Business Suite Release 12 Period End Procedures 20 . since many programs. These processes. Implicit Acceptance Confirm shipments and optionally. 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. Order Management provides seeded close line and close order workflow sub-processes to close the order header and line. so reporting can be limited only to the active orders. windows and report queries retrieve open orders only. appropriate actions should be undertaken to finalize the Order Workflows and close these Sales Orders. Orders marked as closed are not selected. when included in the order header or line workflow. 1. close the status of the eligible order or lines. no lines can be added or changed.

Holds Effect on Eligible Lines * The close order and close line workflow activities will close order or lines if only generic holds are present . perform the above tasks for each operating unit. If you are using Oracle Purchasing to process Internal Purchase Requisitions. no changes can be made to any fields except the descriptive flexfield. Once an order line is closed. Oracle Financials E-Business Suite Release 12 Period End Procedures 21 . the following processes need to be completed: a) Enter and approve all internal purchase requisitions in Oracle Purchasing. 2. 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. Then. b) Run the Create Internal Sales Orders Process in Oracle Purchasing for all requisitions within the current period. Use the Create Internal Sales Orders process to send requisition information from approved. * If you are using external order processing systems for data entry of orders. for which you can define processing constraints. * Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process. Order lines can close independent of each other. Alternatively. the Order Import process is run from within Order Management to generate the internal sales orders. they will not be closed by workflow activity Attention: If MOAC is enabled for the Order Management responsibility. ensure that the processes calling the public API have completed.If orders or lines have activity specific holds present. 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. use the Order Import to update Oracle Order Management from your external systems. inventory-sourced requisition lines to the Order Management interface tables. Use the Error Message window to determine if your data failed to import. It closes the order header if it finds that all the lines are closed. 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. Order Import from Oracle Purchasing for Internal Orders. The Create Internal Sales Orders and Order Import processes can be scheduled to run automatically at specified intervals. if you are using the Order Management public API to create orders.

c) Run Order Import to create internal sales orders from internal requisitions. requisition numbers. 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. Internal orders do not go through the Invoice interface/ AutoInvoice process. Order Management allows you to perform a credit check on customer orders and automatically places orders on hold that violate your credit checking rules. 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. Oracle Financials E-Business Suite Release 12 Period End Procedures 22 . This process will ensure all shipped sales order information is transferred to Oracle Receivables when it reaches the appropriate point in the order workflow. order date ranges. Use the Error Message window to determine if your data failed to import. ship to information. you can access the Workflow monitor to see the order or line status in a more graphical format. f) Invoice Interface / AutoInvoice. e) Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process. 4. From the status page. 3. Review Held Orders Run the following reports to assist with reviewing sales orders on hold: 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. Attention: Order Management does not process internal sales order lines for the Invoice Interface. The Sales Orders window displays the order header status in the main tab of the Order Information tabbed region. scheduled dates. order types. order numbers. and order number. items. as well as credit memos and credits on account created from returns. and internal requisition and internal sales order hold discrepancies. The AutoInvoice Process updates Oracle Receivables for invoice and revenue information. This report includes all open and closed orders. The window shows in tabular format all the activities an order header or line has completed and the corresponding results. The Workflow Status option on the Sales Orders window Tools menu launches the Workflow Status page. credit check rule. currency code. The order line status is displayed in the main tab of the Line Items tabbed region. This report is automatically sorted by customer. Attention: This process is only applicable for Order Workflow Definitions that include the Invoice Interface or Invoice Line processes. This is available through the View Diagram button. even if the Invoice Interface is an action in the order Workflow Definitions for the Internal Sales Order transaction type. for external orders. or identifies why a particular order is on hold.

This report indicates the date and the type of activity for each hold transaction. order type. last shipped date. This report provides detailed line pricing information. and discount information. the revenue recognition process is deferred and linked to customers accepting the shipped goods. and order amount for each order line on hold for each customer you select. order date. 5. purchase order. Review Discounts It is recommended that you review discounts processed as part of the order process to ensure appropriate discount policies have been followed. including the factor for shipments and receivables for a certain number of days. customer name and number. b) Order Discount Summary Report The Order Discount Summary Report reviews discounts applied to orders. In Post-Billing Acceptance. all backordered items and their appropriate line numbers. It is automatically sorted by customer. This report provides order level pricing information. 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. c) Outstanding Holds Report The Outstanding Holds Report reviews order holds for the customer or customers you choose. order date. process cancellations for items/lines which are no longer required. and monetary amounts of both ordered and backordered quantities. once the goods are accepted. shipped and outstanding. selling price. order number. order line. This report displays the order number. order number. Review Backorders Review backlogs and backorders to ensure that these items are current. If necessary. It displays order information such as order number. total quantity both ordered and backordered. invoicing is carried out. a) Backorder Detail Report The Backorder Detail Report reviews all customer orders that have been backordered. 7. order type of each order. Review Customer Acceptances (Optional) In Pre-Billing Customer Acceptance. Use the following reports: a) Order Discount Detail Report The Order Discount Detail Report reviews discounts applied to orders by order line detail. This report provides details for each order including customer name. Oracle Financials E-Business Suite Release 12 Period End Procedures 23 .All balances are calculated as they are using the online credit check rule. including agreement. ordered items. and exceptions are clearly identified and reviewed and/or followed up. This report includes only open orders in an order cycle that includes pick release. and then order line detail. 6. including price list price. and the monetary amounts ordered. salesperson and total order discount. b) Backorder Summary Report The Backorder Summary Report lists all unshipped orders.

If there are no invoices for a particular order that meets the parameter criteria. or deleted as appropriate. These amounts involve totals for shippable items only. 9. Review and Correct Order Exceptions The following reports should be reviewed. Create Service Contracts (Optional) Run the Service Contracts Order Processing Concurrent request to create service contracts for extended warranties. return reason. 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. 10. Oracle Financials E-Business Suite Release 12 Period End Procedures 24 . the workflow activity is set to ‘notified’ instead of being retried. completed. Order Management automatically sorts this report by currency. They may indicate incomplete processing.This report also includes total amounts for customers and currencies. 8. which needs to be corrected. Shipping Execution prints one commercial invoice per delivery within the trip. When Exception Management encounters this situation. A variety of parameters can be used to print the invoice information for a specific order or group of orders. 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. Order Management prints in the report that no invoices exist for that order.) c) Returns by Reason Report The Returns by Reason Report reviews all return material authorizations for various return reasons. b) Retry Activities in Error There are cases when retrying a workflow activity in error will not resolve the problem. Reconcile to Oracle Receivables (Optional) Run the following reports to assist in reconciliation of orders invoiced in the period: a) Commercial Invoice (for all ship dates within the current AR period) The Commercial Invoice Report lists all confirmed shipped items in a delivery. b) Order/Invoice Detail Report The Order/Invoice Detail Report reviews detailed invoice information for orders that have invoiced. and then item. If only a delivery name is specified when defining the parameters of this report. 11. 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.

12. 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. This report provides a summary of each cancelled order, including order number, customer name, line number and item, the date and reason the order or order line was cancelled, the quantity ordered and the quantity cancelled, and who cancelled the order. This report can be used to report total amounts cancelled in a specified time-frame, and allows evaluation of the most common cancellation reasons, review cancellations by salesperson, or review cancellations by customers. b) Salesperson Order Summary Report The Salesperson Order Summary Report reviews orders for one or more salespeople. This report displays the order and each order line associated with each salesperson. Salespeople can use this report to see their current outstanding orders and their status. This report shows open orders, quantity ordered, shipped, cancelled, and invoiced and their potential commission. The report displays all open and closed orders for a salesperson, customer or customer number, agreements, order numbers, order date ranges, order types, line type, and detailed sales credit information for lines in a selected range. c) Customer Acceptance Report Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance.

Oracle Financials E-Business Suite Release 12 Period End Procedures

25

Chapter 4 Oracle Cash Management
This chapter describes the procedures for performing period-end processing in Oracle Cash Management Release 12.

Business Requirements
Oracle Cash Management is an enterprise cash management solution that helps you effectively manage and control the cash cycle. It provides comprehensive bank reconciliation, bank, bank branches & internal bank accounts setup, intra-bank account transfers, cash pooling and flexible cash forecasting. The Bank Reconciliation process enables the verification of entries on the Bank Statement by reconciling that information with system transactions in Oracle Payables, Oracle Receivables and Oracle General Ledger. During the Bank Reconciliation process miscellaneous transactions can be created for bank-originated entries, such as bank charges and interest. Cash forecasting is a planning tool that helps anticipate the flow of cash in and out of the enterprise, allowing the projection of cash needs and evaluation of the company's liquidity position.

Procedures
The following steps are taken in performing period-end processing for Oracle Cash Management. 1. Complete Daily Cash Management Activities Complete bank account transfers for the day, validate them, if necessary, and send payment instructions to the bank. 2. Load Bank Statements Detailed information from each bank statement, including bank account information, deposits received by the bank, and checks cleared needs to be entered into Cash Management. Bank statements can be either manually entered or loaded electronically from information received directly from your bank. For organizations with high transaction volumes bank statements should be loaded and reconciled on a daily basis. Refer to: Entering Bank Statements Manually and Loading Bank Statement Open Interface. 3. Generate Sweep Transactions If you have target balance or zero balance accounts (ZBA) with your banks, you can automatically generate system transactions to match banking information once the bank posts the sweeps. Once the bank statements are imported, run the Sweep Transaction Generation concurrent program. The program will scan the bank statement for sweep lines and, based on the cash pool setup in the system, create sweep transactions between your internal bank accounts, which can be accounted for and subsequently reconciled.

Oracle Financials E-Business Suite Release 12 Period End Procedures

26

4. Create Bank Statement Cashflows If you have recurring items such as bank fees and interest appear on your bank statement, 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, run the Bank Statement Creation concurrent program. This program will scan the bank statement for specific codes, as defined in the Bank Statement Cashflow Mapping, and create cashflows, which can be accounted for and subsequently reconciled. 5. Reconcile Bank Statements Once detailed bank statement information has been entered into Cash Management, the information must be reconciled with the subledger transactions. 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. (Refer to Reconciling Bank Statements Automatically) b) Manual This method requires a manual match of bank statement details with subledger transactions. This method is ideally suited to reconciling bank accounts which have a small volume of monthly transactions. The manual reconciliation method can also be used to reconcile any bank statement details, which could not be reconciled automatically. (Refer to Reconciling Bank Statements Manually) 6. Create Miscellaneous Transactions During the reconciliation process, miscellaneous transactions for bank-originated entries, such as bank charges and errors can be created. Oracle Payables payments or Oracle Receivables receipts can also be manually created. Note: The automatic reconciliation process can be set up to create miscellaneous transactions automatically. Attention: If you create transactions during the reconciliation process, you will need to re-run the ‘Create Accounting’ routine from Oracle Receivables to ensure all information is transferred to the General Ledger. 6a.Complete Bank Transfers Complete the bank account transfer whether it is manual or automatic and record the validation if required before completing the transfer. 7. Review Auto-Reconciliation Execution Report Once the reconciliation process has been completed, reviewing the reconciliation results is recommended.

Oracle Financials E-Business Suite Release 12 Period End Procedures

27

This report shows import and reconciliation errors that occurred when running the Auto-Reconciliation program. Cash Management automatically produces this report during the automatic reconciliation process. You may also request it as needed from the Submit Request window. This report includes either statement import errors, which prevented the automatic loading of your bank statement, or your reconciliation exceptions found during the automatic reconciliation process. This report lists the details of any miscellaneous transactions that were created in Receivables during the automatic reconciliation process. 8. 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. 9. Run Bank Statement Detail Report This report shows statement and transaction information for a specific bank account statement, including bank statement header information, statement line detail, and reconciled transaction detail. This report lists any un-reconciled transactions separately with their current status, and the statement totals for each type of transaction, including the amount entered, reconciled, un-reconciled, over-reconciled and under-reconciled, and gives you the option to select only un-reconciled statement lines. 10. Run Transactions Available for Reconciliation Report This report shows all transactions available for reconciliation for a specific bank account. It lists detailed transaction information for your Available Receipts, Available Payment, and Available Journal Entries for reconciliation. Detailed information includes the Customer, Supplier or Batch Name, Transaction Date, Payment Method, Transaction Number, Currency, and Amount. This report only lists void payments if the Show Void Payments option on the Systems Parameters window is checked. It does not list reversed receipts due to user error nor does it list the associated original receipts that were not reconciled. This report groups transactions by status so that void or reversed transactions are separate from other transactions. 11. Resolve Un-reconciled Statement Lines Resolve the un-reconciled statement lines by manually reconciling the statement lines to the available transactions. 12. 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. The program creates and optionally transfers and posts journal entries to General Ledger. If you do not transfer the journals to General Ledger immediately, you can later submit the "Transfer Journal Entries to GL" concurrent program. Important: Final journal entries cannot be further modified in Cash Management. Please make sure you are satisfied with the draft journal entries before creating final accounting. In addition to creating final accounting entries, the program can be run in a draft mode, in which case draft journal entries will be created. Such journals cannot be transferred or posted to General Ledger.
Oracle Financials E-Business Suite Release 12 Period End Procedures 28

This report lists a balance and an adjusted balance for the bank statement. as well as bank errors. * Transfer journal entry transactions from Oracle Payables and Oracle Receivables to your General Ledger. 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. which were highlighted during the review of the Account Analysis Report. payments. 16. if transfer from sub-ledgers was not in FINAL POST mode. To prevent invalid journal entries to the General Ledger Cash Account enable security rules appropriately. 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. 14. Correct any Invalid Entries to the General Ledger Cash Account (Optional) Reverse or amend any journals incorrectly posted to the General Ledger Cash Account.13. Valid sources will include Payables and Receivables. Run the GL Reconciliation Report Use this report to reconcile the General Ledger cash account to a bank statement balance. Transactions entered directly via General Ledger will have a Source of Manual or possibly Spreadsheet if ADI is used. 15. and journal entries. Warning: To ensure that this report is accurate. you must first perform these tasks: * Reconcile all statements in Cash Management. Oracle Financials E-Business Suite Release 12 Period End Procedures 29 . It also lists a separate adjustment amount for un-reconciled receipts. * Post journals in General Ledger.

the system asks you to resolve the un-posted transactions for those operating units before it allows you to close the period for 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. 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.Chapter 5 Oracle Payables This chapter describes the procedures for performing period-end processing in Oracle Payables Release 12. When you attempt to update the period status to ‘closed’ in one operating unit. Subledger Accounting online inquiry and BI Publisher reports can be utilized to report and analyze balances. so that the general ledger can remain “thin”. Subledger Accounting can contain all of the detailed subledger accounting level analyses. or you are using Internet Expenses or Xpense Xpress. and posting and report processing speed degradation caused by the sheer volume of posted transactions. and their transactions. All of the operating units that share a ledger also share the same period statuses. Where detail level accounting transactions are required to be posted to the General Ledger using sub-ledger accounting (hereafter referred to as SLA). there may be technical constraints involved. Then. The posting level for Oracle Payables must be determined when planning period-end procedures. and reviewed all audit trails for completeness. the system checks for unposted transactions in all operating units within the ledger. relating to the physical data storage volume. If Multi-org Access Control is implemented. Business Requirements Accounts payable activity must be reconciled for the accounting period that is to be closed. ensure you have imported all transactions. If there are unposted transactions in any of the operating units. that period is opened for all operating units within the ledger. When you update the period status to ‘open’ in one operating unit. Procedures 1. 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. period Oracle Financials E-Business Suite Release 12 Period End Procedures 30 . In Release 12 the detailed level of posting can be controlled by GL summarize options and also at SLA journal line type level.

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

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

Payment journal entries debit the liability account and credit the cash account of the bank account used to pay an invoice. 7. if your accounting practices permit it. To create successful accounting entries for accounted transactions with errors.e. you have invoices for which you cannot resolve holds before the close. creating journal entries for these invoice and payment transactions. you might want to use this program to change the accounting date of the transactions to the next open period. This report also provides any errors that may have occurred during generation of the journal entries. The Create Accounting process transfers data to the General Ledger tables. c) The Posted Payments Register This report is used to review the payments posted to Oracle General Ledger during a particular accounting period. For example. 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. 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’. 6. the current accounting period. from Oracle Payables. 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’. for the period that is to be closed. Review the Payables to General Ledger Posting process After Completion. The ‘Unaccounted Transactions Sweep Program’ will not roll forward accounted transactions. Oracle Financials E-Business Suite Release 12 Period End Procedures 33 . and your accounting practices allow you to change invoice distribution GL dates. Submit the Unaccounted Transactions Sweep Program The Unaccounted Transactions Sweep Program transfers unaccounted transactions from one accounting period to another. 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”. and can be used to verify that the total invoice amount equals the total invoice distribution amount. 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. You can then close the current accounting period in Oracle Payables. The following reports can be run to review the invoices and payments that were posted to Oracle General Ledger. a) The Subledger Accounting Program Report generated by the Create Accounting program. The program transfers unaccounted transactions to the period you specify by updating the GL dates to the first day of the new period. Transfer to General Ledger was ‘Yes’ and Post in GL was set to ‘No’. Because you cannot close a Payables period that has unaccounted transactions in it. Posting is determined by the parameter ‘Post in GL’ which is set during Create Accounting. or accounted transactions with errors. i. correct any accounting errors and resubmit the Create Accounting Process.

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. Please refer to the Metalink note # 604739. The report provides details of the outstanding accounts payable liability for the organization. Payables opens the Sweep to Period window. Reconcile Oracle Payables Activity for the Period a) Run the Open Account AP Balance Listing Report This report basically generates the payables trial balance that can be used for reconciliation of the total accounts payable liabilities in Oracle Payables. Accrue Uninvoiced Receipts (Refer to Chapter 7 Period-End Procedures for Oracle Purchasing) 10.1 for more details on this report. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or untransferred journal entries. Oracle Financials E-Business Suite Release 12 Period End Procedures 34 . The Subledger Period Close Exceptions Report lists all accounting events and journal entries that fail period close validation. Choose the Exceptions button in the Control Payables Periods window. Close the Current Oracle Payables Period Close the accounting period by using the Control Payables Periods window to set the Period Status to ‘closed’. Choose the Submit button to submit the Unaccounted Transactions Sweep Program. 2. for a specific accounting period. In the Control Payables Periods window if you try to close a period that has exceptions then the system enables the Exceptions button. 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. Choose the Sweep button. You can accept this default or enter another open period.Payables opens a message window. with the Oracle General Ledger Creditors Control Account.) • Sweep 3. In the Sweep to Period field.To submit the Unaccounted Transactions Sweep Program: 1. Payables provides the next open period. 4. 8. From the window you can choose the following buttons: • Review (This submits the Period Close Exceptions Report. This process automatically submits the Subledger Period Close Exceptions Report.

* Payables Posted Invoice Register . journal entries should be posted for the invoice and payment activity for the period. 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. for reconciliation of Oracle Payables liabilities with Oracle General Ledger’s Creditor Control. For reconciliation of Oracle Payables and Oracle General Ledger when posting is only performed at period end. * Open Account AP Balance Listing Report (for last day of current period).Invoice journals must be posted in general ledger to appear on this report. Also.30th Open Account AP Balance Listing Report =0 Attention: When posting to the General Ledger is performed multiple times throughout each accounting period. Attention: Typical AP/GL Reconciliation Example 31st March Open Account AP Balance Listing Report + April Payables Posted Invoice Register –April Payables Posted Payment Register –. Before running your reports. This is run to generate trail balance as of last day of prior period. third party. * Payables Posted Payment Register . you can use the Account Analysis report and the General Ledger reports to determine what journals are being posted to that account. b) Run Third Party Balances Report This report is used to display balance and account activity information for suppliers and customers. 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 (for last day of prior period). prior to running the report. and third party site * Third party and third party site information * User transaction identifiers for the associated event Oracle Financials E-Business Suite Release 12 Period End Procedures 35 . 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. run the Transfer Journal Entries to GL Program for all transactions in the period that you are reconciling.To obtain the most up-to-date trial balance for a given period. the Posted Invoices Register and Posted Payments Register reports must be run after each posting run.Payment journals must be posted in general ledger to appear on this report. be sure to post the transactions in the general ledger. If the balance reported by the Open Account AP Balance Listing Report does not equal the balance in the AP liability account.

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

The Key Indicators Report provides current activity indicators that compare current period activity with prior period activity in three major areas: suppliers. 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). including RXi. invoices. as well as average values. 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. or BI Publisher to specify which fields of the Tax Reporting Ledger to include and to print the report in a format that meets your needs. and updates. and review the current number of suppliers. Run the Key Indicators Report (Optional) This report enables review of the accounts payables department’s productivity. it includes: Suppliers: * Number of suppliers. payments and matching holds in the system. and payments.The tax extract copies the accounting information from each application and stores it in an interface table. Payables generates reports you can use to review payables transaction activity. When you submit the Key Indicators Report. The following tax registers are available: * Deferred Output Tax Register * Recoverable and Non-Recoverable Tax Registers * Single Cross Product Tax Register * Standard Input and Output Tax Registers The following summary levels are available within each tax register: * Transaction Header * Transaction Line * Accounting Line 14. Oracle Payables produces this report only if you choose ‘Yes’ for the Include Invoice Detail parameter. Oracle Reports. 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. Payables further breaks down each category into basic items. You can use the available reporting tools. * Number of supplier sites. c) Key Indicators State of the System Report The Key Indicators State-of-the-System Report provides a period-end view of Oracle Payables. For example. exception items. invoices. This statistical information can be useful for cash flow analysis and forecasting purposes. when combined with similar information from Oracle Accounts Receivables. Oracle Financials E-Business Suite Release 12 Period End Procedures 37 .

a payment document can pay multiple invoices). However. the system maintains summary information of deleted records to prevent you from entering duplicate invoices or purchase orders. * Average invoices per payment (number of payment documents divided by the number of invoice payments).*Average sites per supplier (number of sites divided by the number of suppliers). Payments: * Number of payments (both manual and computer generated) created and recorded in Payables. and the record will no longer appear on standard reports. * Average payments per invoice (number of invoices divided by the number of scheduled payments). it can no longer be queried. purchase orders. Invoices: * Number of invoices. 15. Matching holds: * Matching holds (number of matching holds in Payables). * Number of invoice distributions. Suggestion: You should create a special responsibility for purging information from Oracle Payables and Oracle Purchasing and assign this responsibility only to the person responsible for purging information from your database. Purge Transactions (Optional) You can delete Oracle Payables or Oracle Purchasing records that you no longer need to access on-line to free up space in your database.) * Scheduled payments (number of scheduled payments based on payment terms and manual adjustments in the Scheduled Payments tab). You can purge invoices. Warning: After a record is purged. * Average lines per invoice (number of invoices divided by the number of distributions. * Average matching holds per invoice on matching hold (number of matching holds divided by the number of invoices on matching hold). and related records such as invoice payments and purchase receipts. * Invoice payments (number of invoice payments made by Payables . Oracle Financials E-Business Suite Release 12 Period End Procedures 38 . suppliers.

required if OM-shipping is used) If you import transactions from an external system or Oracle Projects. Reconcile Transaction Activity for the Period Reconcile the transaction activity in Oracle Receivables. and reviewed all audit trails for completeness.Chapter 6 Oracle Receivables This chapter describes the procedures for performing period-end processing in Oracle Receivables Release 12. Posting to the General Ledger allows the extraction of details from Oracle Receivables. 2. Credits and Adjustments * Complete Receipts and Reversals * Complete Invoice and Customer Import * Complete Lock Box Processing * Run the revenue recognition program (Optional. This reconciliation process checks that Oracle Receivables transactions are balanced. before posting to the General Ledger using SLA. Transaction Register Oracle Financials E-Business Suite Release 12 Period End Procedures 39 . Business Requirements Oracle Receivables requires periodic internal reconciliation of the transactions entered into the Accounts Receivables system. receipts. Procedures The following steps are taken in performing period-end processing for Oracle Receivables. Run the following reports for the same accounting period date range: a. ensuring that all items eligible for posting are reflected on the Sales Journal. After posting to the General Ledger. Completing all transactions for Oracle Receivables: * Complete Invoicing. and accounts balances. 1. it is possible to reconcile Oracle Receivables with the General Ledger by verifying that all the correct journal entries were made. The application provides the functionality to enable reconciliation of your sub-ledger. Oracle Receivables provides a comprehensive set of reports to facilitate the reconciliation of outstanding customer balances. ensure that you have imported all transactions and master files. and the creation of journal entries in the General Ledger. transactions. before posting to the General Ledger. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed.

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

use the AR Reconciliation report to confirm that your transactional and accounting data match. When you update the period statuses to ‘Open’ in one operating unit. However. even if the data matches. * GL Subledgers Not AR . If the actual balance of a specific account is different in Receivables than in GL. the journals could still post to incorrect GL accounts. During the internal reconciliation process.Unposted journals in the general ledger. that period is opened for all operating units within the ledger. and * You have reviewed the Unposted Items report to confirm that all journal entries have posted.Journal entries posted to the General Ledger from other subledgers.The AR to GL Reconciliation report compares the account balances in Oracle Receivables to those in Oracle General Ledger. and * You have used the posting execution reports to confirm that the journal entries exported from Receivables match those posted in General Ledger. Reconcile Outstanding Customer Balances Reconcile the outstanding customer balances at the beginning of a specified period with the ending balance for the same period. thus creating reconciliation issues in Oracle General Ledger. known as the Roll Forward Formula: Period-End Balance = Outstanding Balance at Start of Period + Transactions + Adjustments .Unapplied Receipts The following list represents the various components that affect a customer’s balance and the reports. Run the AR to GL Reconciliation report: * After the Create Accounting program in Receivables has completed. which can be run and reviewed to reconcile these components: Component Beginning Balance Report Aging reports Oracle Financials E-Business Suite Release 12 Period End Procedures 41 . then the following columns highlights the type of journals that affect the account balances: * GL Source Manual . The Difference column indicates how the activity in Receivables compares to the journal source of Receivables in the General Ledger. This report simplifies the reconciliation process by comparing Receivables and General Ledger account balances in a single place. 3. using the following formula. Attention: Where there are multiple operating units within the same ledger all operating units must be ready to close at the same time.Invoice Exceptions Applied Receipts . This report will show a difference between Receivables and GL account balances only if items did not successfully post to GL accounts. All of the operating units that share a ledger also share the same period statuses.Manual journal entries made in the General Ledger. such as Oracle Payables or a legacy feeder system. and highlights journal sources where discrepancies might exist. * Unposted in GL . The Potential Reconciling Items report addresses this issue by suggesting journal items that might potentially post to GL accounts with unexpected account types.

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

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. Bug 7589198: Receipt Register does not match Receipt journal – deemed functionality (similar to Bug 7423482). 7. This program is owned by SLA and can be run both from the transactions screen and also from the SRS screen. Both reports display invoice related receipts and miscellaneous receipts. 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). Bug 7423482: Receipt Register and Receipt Journal do not show on-account activity – deemed functionality. Account balances for transactions and receipts can be reconciled by generating the Sales Journal by GL Account Report. Once transactions and receipts have been transferred to the GL tables. Post to the General Ledger Prior to posting to the General Ledger.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. for transfer to the General Ledger. it is possible to perform external reconciliation during and after the posting process.1: Unable to Reconcile Receipt Register to Receipt Journal – Enhancement 5567693 is still pending. transactions in error etc. The posting process for Oracle Receivables involves a single step: Create Accounting This request-owned by SLA can be submitted from the transactions screen or even from the SRS screen. 8. The account totals in the Oracle Financials E-Business Suite Release 12 Period End Procedures 43 . 6. Compare this report to the Journal Entries Report (run in Posted status mode) and verify that they match. If Create Accounting is submitted in the ‘Final’ mode without transferring it to the General Ledger. Create Accounting will generate a report which details the transferred transactions. 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. Oracle Receivables regards these items as having been ‘posted’ within the sub-ledger. the entries will have to be transferred separately. Use the same General Ledger date ranges for the Journal Entries Report and the Create Accounting program. See the following Metalink bugs and enhancement requests for more details: Note 393682. the Receipts Journal Report (in ‘transaction’ mode) and the Journal Entries Report for posted items. Reconcile Receipts to Bank Statement Activity for the Period (Refer to Chapter 4 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. After internally reconciling the transactions and receipts using these two reports. Unfortunately currently (February 2009) this is not always the case.

Print Invoices Once you are satisfied that the customer balances are reconciled.Sales and Receipt journals should match the corresponding account balances in the Journal Entries Report. and compare the sum total with the Journal Import Execution Report. Attention: If the customer is using Reporting/Accounting sequences. then SLA accounting is displayed. the following statements apply: If SLA final accounting lines exist. and comparing them with the Journal Entries Report output. 11. ensure all the invoices generated during the month have been printed and issued. Close the Current Oracle Receivables Period Close the current period in Oracle Receivables using the Open/Close Accounting Periods window. which users can copy and modify the report template according to their needs. 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. No or ALL. If the Balance Forward Billing functionality is used. 10. 9. If SLA accounting lines do not exist. refer to the Oracle Receivables Implementation Guide or the Oracle Receivables User Guide. Attention: The ‘Detail by Account’ version of the Journal Entries Report may be the most useful for reconciliation in this case. they can run Journal Entries Report unsing Sequence Ranges created in the Create Accounting program run. Note: Balance Forward Billing replaces consolidated billing invoices (CBI) feature of 11i. 12. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or un-transferred journal entries. Reconcile the Journal Import by manually reviewing the transactions in the Subledger Accounting Program Report. 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 Oracle Financials E-Business Suite Release 12 Period End Procedures 44 . When running any Oracle Receivables reports that display accounting involving transactions that have been posted to GL. Reconcile the Journal Import Process Create Accounting program submits Journal Import automatically when launched in ‘Mode = Final’ and ‘Transfer to GL = Yes’. For more information on the setup of balance forward billing. 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. then AR distribution accounting is displayed. ensure that the consolidated (BFB) invoices have been generated for the current period.

Using the Submit Requests window to generate this report. Oracle Financials E-Business Suite Release 12 Period End Procedures 45 . which is required to be reported to the relevant Tax Authority. This report is used to display balance and account activity information for Suppliers and Customers. including withholding tax. submit with a GL date range for at least the current financial year. Open the Next Oracle Receivables Period Open the next period in the Oracle Receivables using the Open/Close Accounting Periods window. 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. then re-open both appropriate Receivables and General Ledger Periods and initiate another posting. Reconcile Posted Journal Entries After running the GL posting process in Oracle General Ledger. 17. This report is owned by SLA. It only includes journal entries transferred to and posted to the General Ledger. Note: To avoid duplication with subledger journal entries. Third Party Balances Report Run Third Party Balances Report from the SRS screen.13. This report should not generate any output if all Receivables transactions have been successfully posted to the General Ledger. run the Journal Entries Report (with ‘Posted = Y’) to help reconcile the posted journals. 18. 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. If there are any items not posted for the current or prior periods. Run Reports for Tax Reporting Purposes (Optional) A variety of standard reports can be used to provide tax information. for the transactions. Run the request from the Submit Requests window. General Ledger journal entries imported from Subledger Accounting are not included in the report. third party. 16. 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. The output will consist of all items not posted to the General Ledger for the specified GL date range. which were transferred in FINAL mode and with Post in GL being set to NO. 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. 15. 14. Review this report and compare it with the Third Party balances report.

The Selection and Validation and Archive processes form the Archive-Preview program. Alternatively. Output from the tax extract is designed to look as close to a simple tax report as possible. The final process is to transfer the archive data to a separate storage medium. and to print the report in a format that meets your needs. Archive. 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 19. Run Archive and Purge Programs (Optional) The Archive and Purge cycle is divided into four separate processes: Selection and Validation. then stores this information in the archive tables. validates the data to identify the transaction chains. You can use the available reporting tools. archive. and optionally Copying to a file. Oracle Reports. The Purge program uses the information in the archive tables to delete eligible transactions from the database tables. Purge. Warning: You should not use the Receivables Archive and Purge program if you are using cash basis accounting. Oracle Financials E-Business Suite Release 12 Period End Procedures 46 . including RXi. or XML Publisher to specify which fields of the Tax Reporting Ledger to include. The tax extract copies the accounting information from each application and stores it in an interface table.The E-Business Tax data extract draws tax information from each application and stores the data in an interface table. and purge processes together using the Archive and Purge program. you can run selection and validation. This program selects eligible transaction using criteria you had specified.

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. Requestors can create receipt transactions by responding to the notification. a Routing of Direct Delivery. Review the Outstanding and Overdue Purchase Orders (Optional) Run the following reports: Oracle Financials E-Business Suite Release 12 Period End Procedures 47 .g. 2. 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. notify requestor requisition has been approved). 1.Chapter 7 Oracle Purchasing This chapter describes the procedures for performing period-end processing in Oracle Purchasing Release 12. Closing FYI notifications is Optional. or are FYI notifications only (e. Users should close all FYI notifications and respond to those that require a response. Business Requirements The purchasing activity must be reconciled for the accounting period that is to be closed. The Confirm Receipts workflow sends notifications for items with a Destination or Deliver–To Type of Expense. 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. d) Print or Archive all new Purchase Orders e) Respond to all Workflow Notifications Notifications may either require action (e. 3. and the next five periods. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed. or Notification Details Web page (accessible through the Notifications Summary menu in Purchasing) to requestors or buyers who create requisitions in Purchasing or iProcurement. e–mail. notify approver approval required).g. You can also use the report when negotiating with a supplier by limiting the commitments to a specific supplier.

7. The quantity ordered and quantity received is displayed so the status of the purchase orders can be monitored. the appropriate department can use the details obtained from the Purchase Order Detail Report. Run the Receipt Accruals . but the receipt has not been entered into Oracle Purchasing. before creating receipt accruals for that period.* 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. 5. It is not necessary to enter all the receipts for a period prior to closing that period. to enable the creation of receipts accrual entries. where possible. Journal entries are created for the amount of the receipt liabilities. the appropriate department can then follow up with the supplier. Follow Up 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. 6. Simply backdate the receipt date when entering receipts for a closed period. to follow up the status of the ordered items with the suppliers . or planned purchase orders. Oracle Financials E-Business Suite Release 12 Period End Procedures 48 . which corresponds to the Oracle Purchasing period being closed. and resolution of any invoice holds. This report indicates exactly what has to be accrued. and helps in the preparation of accrual entries. the receipt transaction needs to be entered by the appropriate personnel. Entering of invoices. Follow Up Receipts . Oracle Purchasing creates an un-posted journal entry batch in the General Ledger for the receipt accruals. Complete the Oracle Payables Period-End Process Complete the steps to close the Oracle Payables period. make sure that all receipts have been entered for a specific period.Check With Suppliers For purchase orders not received. debiting the charge account and crediting the Expense AP Accrual Account. 4.Period-End Report to create period-end accruals for uninvoiced receipts. matching of unmatched invoices. 8. should be carried out at this point in the period-end process. for Expense distributions for a specific purchasing period. Performing the Oracle Payables Period-End process effectively prevents any further invoices or payments being entered into Oracle Payables for the closed period. Attention: Where you have selected to accrue receipts at period end. Warning: Where you have Oracle Inventory installed. Receipt accruals can be reviewed by account and by item. for what amount. Each time the process is run.Period End Process Run the Receipt Accruals . specific standard. using the details from the Uninvoiced Receipts Report. If the goods have been received. 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.

on the Accrual tabbed region of the Purchasing Options window for the current Organization. then the accrual entries need to be reversed manually. Manually remove the Invoice Price Variance amount from the AP Accrual Account using your General Ledger. Reconcile Accrual Accounts . 9.If encumbrance or budgetary control is being used. which in turn will trigger the journal import. a reversal is not required. Oracle Financials E-Business Suite Release 12 Period End Procedures 49 . 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. This process can be run as many times as needed.(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. Oracle Purchasing reverses the encumbrance entry when creating the corresponding accrual entry. Attention: This step is only required if the Accrue Expense Items flag is set to Period End. If encumbrance or budgetary control is being used. The Create Accounting Program has to be run to create SLA journals. Attention: The Receipt Accruals Period End Program creates accounting in the receiving sub ledger only. another journal entries batch is created. 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. 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’.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 * Inventory Account . When the Accrue Expense Items flag is set to At Receipt. corresponding to the encumbrance reversal entries for the un-invoiced receipts that were accrued.

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. Run the Invoice Price Variance Report for the current period. The Accrual Reconciliation Reports are used to analyze un-invoiced receipts. 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. These reports enable you to identify the following issues in receiving. work in process. inventory. distinguish accrued receipts from invoice price variances. purchasing.Identify the Invoice Price Variances amount and Accrued Receipts amount in the AP Accrual Account. 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. and to reconcile the balance of the AP accrual accounts. 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. 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. d) Summary Accrual Reconciliation Report Oracle Financials E-Business Suite Release 12 Period End Procedures 50 . 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. and identify errors. At any given time.

more entries must be reconciled in the AP accrual accounts. the Accrual Write-Offs window can be used to indicate which entries are to be removed and written off from this report. 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. you temporarily record an accounts payable liability to your expense or inventory AP accrual accounts. After researching the reported accrual balances. The Reconciliation reports also provide information on the quantity differences (between the quantity received for a purchase order shipment and the quantity invoiced). * If you have installed Oracle Inventory or Work in Process. If you also receive inventory. You can accrue both expense and inventory purchases as you receive them. this report enables reconciliation with the accounts payable accrual account. these differences are resolved. and inventory receipts are not performed. If expense purchases are accrued on receipt. * If expense purchases are accrued at period end. Accounting entries have to be created in SLA and GL for these write-off transactions by submitting the Create Accounting program. Oracle Financials E-Business Suite Release 12 Period End Procedures 51 . Ensure that prior to closing the period. When this happens. For Oracle Payables. and Oracle Work In Progress. all transactions are created in Purchasing and need the GL Transfer Program to be run to transfer to the General Ledger. and price differences. and hence manual adjustment of accrual entries is not required. the Accrual Reconciliation Report also displays any inventory or work in process transactions for the accrual accounts. Oracle Payables clears the AP accrual accounts. a GL transfer or period close must first be performed for the transactions to appear on these reports. no information will be available to report. When Oracle Payables creates the accounting for the matched and approved invoice. Prerequisites: * Oracle Payables and Oracle Purchasing installed. Attention: Most commercial installations accrue expense receipts at period end. the Receiving Value Report by Destination Account must be run to break out the receiving/inspection value by asset and expense. Attention: For Oracle Purchasing. * If expense purchases are accrued on receipt. The Reconciliation Reports can help in monitoring potential problems with purchasing and receiving activities that can affect the accuracy of 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.The Summary Accrual Reconciliation Report can be used to analyze the balance of the AP accrual accounts. journal entries must be created for the invoices. For Oracle Inventory. as the information is not required as the receipt occurs.

Use this report to review the accounts encumbered. Therefore. before commencing the year end Encumbrance processing in Oracle General Ledger. the encumbrances on the Encumbrance Detail Report remain until payment information from Payables is transferred to General Ledger. * Carry forward the funds available as at the end of the year.10. * Carry forward encumbrances. the Encumbrance Detail Report reflects the true periodend receipt information. The Encumbrance Detail Report reflects activity from General Ledger. an automated process transfers the receipt information to General Ledger using the Journal Import Process. 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.) 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. if the encumbrance option for requisitions or purchase orders has been enabled. Payables transfers only accounting information for paid invoices to the General Ledger. not on receiving information. * Period-end accrual . or to a separate budget to identify between current year and carry forward amounts if required. the encumbrance detail on the report is based on invoice matching information from Payables. (Refer to Chapter 11 Period-End Procedures for Oracle General Ledger. Attention: You must complete the Year End Encumbrance processing in Oracle Purchasing. * Cash basis . * Carry forward budgets into the current appropriation budget. Oracle Financials E-Business Suite Release 12 Period End Procedures 52 .Generate the Encumbrance Detail Report at period-end. is to extinguish any outstanding encumbrances or unused funds when you close the last period of the Financial Year within Oracle General Ledger. not Purchasing or Oracle Payables. When cash-basis accounting is used and the Payables Transfer to General Ledger process is submitted. and the encumbered budget. The default processing for Oracle Financials at year end. Mass budget processing also allows you to combine these budgets. During the period.If cash-basis accounting is used. use the Encumbrance Detail Report in a way that matches the accounting method: * Receipt accrual . After the Receipt Accruals Period-End process is run. and requisitions and purchases have entered and approved. Upon entering receipt delivery information. The carry forward process enables managers to perform any of the following: * Carry forward encumbrances for existing transactions (purchases / requisitions).Generate the Encumbrance Detail Report as needed when the Accrue at Receipt option is used. Other facilities available: * Use mass allocations to bring forward part of the funds available.

you have the option of canceling the original requisition at the same time. Oracle Purchasing creates journal entries to zero out the encumbrances associated with the canceled requisitions and purchase orders. 12. as well as any of the following: * Document Type * Supplier Name * Accounting Flexfield Range This process will automatically generate a MassCancel 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 MassCancel When this process is run. 11. Define MassCancel The Define MassCancel window is used to nominate a date range for transactions. Open the Next Oracle Purchasing Period Open the next purchasing period in the Control Purchasing Periods window. Note that when canceling a purchase order. 13.Based on this report you can identify those transactions that you wish to carry forward into the new financial year. b) Perform MassCancel in Oracle Purchasing (Optional) MassCancel enables the cancellation of requisitions and purchase orders on the basis of user selected criteria. 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). Attention: If you wish to cancel both purchase orders and requisitions. Close the Current Oracle Purchasing Period Close the current Purchasing Period in the Control Purchasing Periods window. Refer below for the steps required to cancel transactions that are not to be carried forward. you must initiate MassCancel twice. Run Standard Period End Reports (Optional) * Suppliers Quality and Performance Analysis Reports a) Suppliers Report Oracle Financials E-Business Suite Release 12 Period End Procedures 53 .

The report lists all site names and addresses of each potential duplicate supplier. early shipments. all divided by the total corrected received quantity. This report can be used to derive a supplier service penalty by multiplying the days variance quantity by a percentage of the price. d) Supplier Service Performance Analysis Report The Supplier Service Performance Analysis Report lists late shipments. b) Suppliers Audit Report Use the Supplier Audit Report to help identify potential duplicate suppliers. The % Received Early is the percentage of the ordered quantity received before the promise date and outside the receipt tolerance days. If purchase order information is merged. and shipments to wrong locations. This report also shows if a supplier is on PO Hold. and auto source rules are updated to the new supplier. You have the option to include supplier site address and contact information. The % Received Late is the percentage of the ordered quantity received after the promise date and outside the receipt tolerance days. After duplicate suppliers have been identified. Use the report to compare actual purchase percentages with sourcing percentage. This report is useful for identifying suppliers with quality performance issues. special characters. etc. The report ignores case. they can be combined using Supplier Merge. This report lists active suppliers whose names are the same. then any references to the supplier in blanket purchase orders. up to a specified number of characters. spaces. but within the receipt tolerance days or not past due. The % Open Past Due is the percentage of the ordered quantity not received by the promise date and beyond the receipt tolerance days. Oracle Financials E-Business Suite Release 12 Period End Procedures 54 . quotations. e) Supplier Volume Analysis Report The Supplier Volume Analysis Report shows the dollar value of items purchased from a supplier. The % Received On Time is the percentage of the ordered quantity received on the promise date or within the receipt tolerance days. for percents accepted. c) Supplier Quality Performance Analysis Report The Supplier Quality Performance Analysis Report can be used to review suppliers' quality performance. The % Open Current is the percentage of the ordered quantity not yet received. The report prints the items that are assigned sourcing rules. The result is the quantity per day the supplier is in variance. Payable inserts a blank line between groups of possible duplicate suppliers. 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.Use the Suppliers Report to review detailed information entered for a supplier in the Suppliers and Supplier Sites windows. Payables lists your suppliers in alphabetical order and you can additionally order the report by supplier number. rejected. rejected shipments. and returned.

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. Purchasing prints the blanket agreement or planned purchase order header information. The Negotiated Amount is the product of the price on the quotation and the quantity ordered. The Actual Amount is the product of the actual price listed on the purchase order line and the quantity ordered. The Amount Saved is the negotiated amount less the actual amount. quote. using blanket purchase agreements and planned purchase orders. For each blanket purchase agreement and planned purchase order created. if no release exists. * Review Quotation.The Expenditure is the sum of the item line amounts for standard purchase orders for the supplier. the line price was from the Quote. the line price was from the Market Price. Purchasing prints the product of the market price of Oracle Financials E-Business Suite Release 12 Period End Procedures 55 . or list price to the actual price. * Analyze Requisitions Requisition Activity Register The Requisition Activity Register shows requisition activity and monetary values. Purchasing prints the requisitions in order of creation date and prepared name. with negative figures in parentheses. The Negotiated Amount is the product of the price on the quotation and the quantity ordered. * Savings Analysis Reports a) Savings Analysis Report (by Category) The Savings Analysis Report (By Category) shows buyer performance by category. The Intended Commitment is the total expenditure multiplied by the split percentage entered in the sourcing rules. RFQ and Purchase Order Statuses Purchase Order Statuses may optionally be reviewed early in the period close processing for Oracle Purchasing. Purchasing prints the product of the market price of the item ordered and the quantity ordered. Use the report to compare the market. If the line price type is M. If the market price is not defined. If a quote is not defined. Purchasing uses the list price. Purchasing provides the detail of the releases created against these orders. the line price was from the List Price. If the line price type is Q. b) Savings Analysis Report (by Buyer) The Savings Analysis Report (By Buyer) shows buyer performance by purchase order. 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 Actual Percentage is the items expenditure as a percentage of the total expenditure for the date range of the report.

and if the line price type is L. If the line price type is M. the line price was from the Market Price. The Actual Amount is the product of the actual price listed on the purchase order line and the quantity ordered. * 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. Purchasing uses the list price. with negative figures in parentheses. the line price was from the Quote. The report includes a price type Legend at the bottom of each page for the price type. Use this report to review the encumbered accounts. 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 56 . and there are entered and approved requisitions and purchases. If the market price is not defined. the line price was from the List Price. If the line price type is Q. The Amount Saved is the negotiated amount less the actual amount. * Cancellation Reports Use these reports to review all cancelled purchase orders and requisitions.the item ordered and the quantity ordered.

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

Any adjustments to the period can be made via new inventory transactions as required. Check Inventory and Work in Process Transaction Interfaces Check the Interface Managers window to ensure that there are no unprocessed background or concurrent programs. 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. then at month end before closing.2. for the order-shipments which have been invoiced in AR. Though the accounting period can be closed. 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. once it is closed these transactions cannot be processed in that period. Since a period. correct the error at the source. 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. Attention: This process needs to be completed for each defined Inventory Organization. 4. uncosted material transactions. This will display transactions under the following statuses: * Resolution Required: Displays the number of unprocessed material transactions. depending on INV profile option “TPINV: Transaction Processing Mode”) * Move Transaction Manager (for IWIP) 3. These must be resolved before the period is closed. Transfer Summary or Detail Transactions If Order Management is used. and pending IWIP costing transactions existing in this period. revenue recognition has been processed in AR. cannot be re-opened. Oracle Financials E-Business Suite Release 12 Period End Procedures 58 . running this process prior to closing the period facilitates validating the interfaces transactions. The interface managers that need to be run are as follows: * Cost Manager (mandatory) * Material Transaction Manager (Optional. pending material transactions. once closed. and the accounting entries between ‘Deferred COGS account’ and ‘COGS account’ must be generated in INVCST. In case of error. and pending shop floor move transactions existing in this period. * Resolution Recommended: Displays the number of pending receiving transactions.

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

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

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

Chapter 9 Oracle Assets This chapter describes the procedures for performing period-end processing in Oracle Assets Release 12. 1. 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. Assign All Assets to Distribution Lines If an asset has not been assigned to a distribution line. Oracle Assets has only a single open depreciation period in each asset book. Complete All Transactions for the Period Being Closed Ensure that all transactions have been entered for the period being closed. Run Calculate Gains and Losses (Optional) The Calculate Gains and Losses program for retirements can be submitted prior to running depreciation. and will not close the period. The Calculate Gains and Losses process is performed independently for each depreciation book. 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. Business Requirements At period end. the period end Depreciation Process will not complete. The book and depreciation period are nominated on the Submit Request window. 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. Check that transactions are not being entered as Oracle Assets prevents transaction data entry while the Depreciation Run Process is running. Oracle Financials E-Business Suite Release 12 Period End Procedures 62 . Completing all transactions for Oracle Assets: * Prepare and Post Mass Additions * Complete Manual Additions * Complete Adjustments * Complete Retirements * Complete Transfers * Complete Reinstatements 2. Once a depreciation period in Oracle Assets has been closed. it cannot be re-opened.

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

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

the Assets Journals will be posted automatically in the next scheduled posting run. b) Account Drill Down Report– Reconcile journal entries to the General Ledger. use the More Actions button to Post each Journal individually or fin the source of Assets has been included in the Auto Post options. Optionally. 10. The report gives detailed information of the asset transactions represents by a journal entry line. b) Tax Reserve Ledger Report Additionally. the Account Reconciliation Reserve Ledger Report can be run. Oracle Financials E-Business Suite Release 12 Period End Procedures 65 . Reconcile Oracle Assets to the General Ledger Using Reports * Reserve Ledger Reports a) Journal Entry Reserve Ledger – Reconcile. * 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– Reconcile the batch totals from this report with those of the General Journals Report in Oracle General Ledger run for posting status = ‘Unposted’.Post each journal entry batch using the Post Journals window in Oracle General Ledger to update the account balances. The report enables detailed review of the account activity on a specific general ledger account.reconcile with the Account Analysis with Payables Details Report.

* Allow Purge for the book in the Book Controls window before you perform the purge. Prerequisites: * If necessary. See: Defining Depreciation Books. 11. Oracle Financials E-Business Suite Release 12 Period End Procedures 66 . In the first stage drilldown happens from GL to SLA. This can be done at cost centre level for direct comparison with the Asset Cost Summary and Reserve Summary reports. * General Ledger Reports a) Unposted Journals Report– Run. 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 12.run the General Journals Report for Posting Status = Posted. then your financial statements will also be inaccurate. You can only restore the most recently purged fiscal year. so you must restore fiscal years in reverse chronological order. 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. you can archive and purge historical data to free hardware resources.run the General Journals Report for Posting Status = Unposted to reconcile with the Drill Down reports. b) Posted Journals Report– Run. If the asset inventory is inaccurate. See: FA: Archive Table Sizing Factor. c) Account Analysis Report with Payables Detail – The ending balance of this report reconciles with the Reserve Summary Report ending balance. update the ‘FA: Archive Table Sizing Factor’ profile option. Archive and Purge Transactions (Optional) If you no longer need to run reports for previous fiscal years.Note: Drilldown is a two-stage process. d) Financial Statements Generator – It is recommended that you create a detailed Financial Statement Generator (FSG) for all asset accounts.

b) Open the Archive and Purge window. c) Enter the Book and Fiscal Year you want to archive. g) Choose Purge to submit a concurrent request that changes the status from Archived to Purged and removes the archived data from Oracle Assets tables. Oracle Financials E-Business Suite Release 12 Period End Procedures 67 . d) Choose Archive to submit a concurrent request that changes the status from New to Archived and creates temporary archive tables with the data to be purged.To archive and purge transaction and depreciation data: a) Change Responsibilities to Fixed Assets Administrator. e) Export the archive tables to a storage device. You must archive and purge in chronological order. Now your database administrator can drop the temporary archive tables. f) Return to the Archive and Purge window and use the Archive Number to find the archive you want to purge. Note: The temporary table name includes a five-digit archive number. You can only purge definitions with a status of Archived or Restored. Oracle Assets automatically assigns an Archive Number when you save your work.

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

If you find the results to be incorrect. 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.You can view and delete these period adjustments. Transfer Journals to General Ledger After you enter and verify all accounting changes for the journal. delete them and review the corresponding financial instrument. 5. but you cannot change them. re-create the accruals. Treasury sends the journals directly to GL and not via SLA. 4. * Authorize the results. Once the financial instrument is correct. you cannot change any of the accounting for the batch in Treasury. Oracle Financials E-Business Suite Release 12 Period End Procedures 69 . Attention: At this moment for the current version (12. and reallocate suspense journal entries to a GL account. view the generated journal entries.6) there is no integration yet with SubLedger Accounting (SLA). change the dates or GL accounts for your journal entries. Generate Journals Use the Daily Journals window to generate the daily journals for an accounting batch.0.

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

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

This process can be submitted for foreign currency and for multiple ledgers. Generate Mass Allocation Journals (Optional) Select the Mass Allocation Journals that require generation for the current period. use the GL_Interface. * Run the Journal Import process for these sources and ensure the resulting Journal Entries are posted either automatically by AutoPost or manually.General Report c) Journals .Entry Report Oracle Financials E-Business Suite Release 12 Period End Procedures 72 . the accounting journal details will automatically by stored in the XLA tables. 8. Ensure that all entries to the source accounting flexfields used in the MassAllocation Journal definitions are finalized for the current period.e. 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. perform the calculation and post. This process can be run across ledgers. If you are using Oracle Financials Accounting Hub to generate accounting for your 3rd party systems. Attention: Journal entries can be reviewed on-line. Reviewing journal entries prior to posting minimizes the number of corrections and changes after posting. prior to being transferred (in summary or detail) and imported into Oracle General Ledger. provided the access is available. Submit the process to generate the Reversal Journals. for each successive level of allocation entry). 7. perform any journal entry updates. 6. Generate Recurring Journals (Optional) Select all the Recurring Journals that require generation for the current period. Submit the process to generate the Recurring Journals. prior to generating the journal. Review and Verify Journal Details of Unposted Journal Entries Review any remaining unposted journal entries for the current period. non-Oracle subledgers has been transferred to Oracle General Ledger. or via reports. including any adjusting entries. Standard Journal reports available included: a) Journal Batch Summary Report b) Journals .4. 5. Generate Reversal Journals (Optional) Select all the Journals to be reversed. Note: If you are loading accounting journals for 3rd party systems directly to Oracle General Ledger. Post step-down allocations in the correct order (i. Following review of journal entry batches. This process can be run across ledgers and across currencies. before posting. Update journal entries as appropriate.

Post Budget batches to any period in an open budget year. recurring and allocation journals.General Report with a Posting Status of Error Journals to review error journal entry batches and their journal entries. 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. Oracle Financials E-Business Suite Release 12 Period End Procedures 73 . Post Encumbrance batches to any period up to the last period in the latest open encumbrance year. Locate the problems with unpostable journal entry batches using the following information: a) Control Total When using a control total. Post updated journal entries.Line Report e) Tax Journals Report f) General Ledger . Review the results of the post: * The Posting Execution Report facilitates review of the results of journal entry posting. * Run the Journals . c) Batch Status Oracle General Ledger describes the problems with unpostable batches. b) Period Status Post Actual batches to open periods. and the corrected journal entries re-submitted for posting.d) Journals . ensure that the debits and credits equal the control total. including reversal. Post All Journal Batches Post all journal entries for the current period. This report indicates any errors in journal entries or journal entry lines were discovered during the posting process.Entered Currency g) Journals by Document Number Report (when document sequencing is used) 9. Update unpostable journal entries. Oracle General Ledger generates this report every time posting of journal entry batches occurs.

Request financial reports such as: a) Balance Sheets e. discard any obsolete versions of your report for that accounting period.g. Translatae account balances to any defined currency. Revalue Balances (Optional) Revalue account balances to update functional currency equivalents. 10. Maintain period-end exchange rates for all foreign currencies to which you want to translate. Whichever you choose you can run your extract programs to extract the data from General Ledger to the consolidation systems. it is advisable to create a standard period-end accounting report set that can be run at each period end. Consolidate Ledgers (Optional) Attention: You can consolidate using Global Consolidation System. Custom accounting reports can be created by using the ‘Financial Statement Generator (FSG)’. Maintain average exchange rates for all foreign currencies to which you want to translate. * Consolidate within ledgers a) Enter consolidating journal entries Oracle Financials E-Business Suite Release 12 Period End Procedures 74 . 13. Maintain historical rates or amounts for any owner’s equity accounts to be translated. Translate Balances (Optional) Define any new currencies to which accounting balances are to be translated. Financial Consolidation Hub or the Hyperion Consolidation functionality. 12. 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.9a. Run GL Trial Balances and Preliminary Financial Statement Generator Reports (FSGs) To maintain a consistent audit trail. Detail Trial Balance Report b) Income Statements c) Gross Margin Analyses 11. Run the Period Close Exceptions Report This is a new step in Release 12. and ensure a follow-up with relevant colleagues if any exceptions are identified. Suggestion: To prevent confusing different versions of accounting reports for a specific accounting period.

* Consolidate 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 * Consolidate across ledgers using the Global Consolidation System (GCS) a) Define consolidations. use recurring journal entry formulas. intercompany sales etc. enter the consolidating entries to a separate company. c) Run consolidations. Oracle Financials E-Business Suite Release 12 Period End Procedures 75 . and the corrected journal entries re-submitted for posting. Suggestion: To automatically generate the amounts and accounts for consolidating and eliminating journal entries.The following two methods can be used to create eliminating entries for multiple companies using a single Ledger: Automatic Eliminating Entries . Suggestion: To produce financial reports that reconcile your consolidating companies with the consolidated totals.use formulas b) Post consolidating journal entries. Attention: All errors in the journal entry batches must be fixed. c) Define a reporting hierarchy that consolidates all the companies. d) Define financial statements with the reporting hierarchy. and build reports with a separate column for ‘consolidating entries’.define mapping rules to eliminated intercompany receivables. f) Analyze results using drill-down capability from Parent ledger to Subsidiary ledger/s. payables. Recurring Journals. b) Perform revaluation and translation of foreign subsidiaries as required. e) Report on this consolidated ledger using FSG’s. d) Enter consolidated and eliminating entries. investments in subsidiaries.

Review and Correct Balances (Perform Reconciliations) Oracle General Ledger should be reconciled with all other modules. With General Ledger Entry Reconciliation. unposted or error journal entries and report on a specific batch or on journal entries from a specific source. b) Accounts Analysis Reports These reports list the accumulated balances of a range of Accounting Flexfields and all journal entries that affect that range. A new. The report provides detailed information on each journal entry line including source. Create and post adjusting journals to correct errors in account balances. and is also fully integrated with SLA. you can selectively cross-reference transactions in GL with each other by entering reconciliation reference information at the journal line level. general journals. Detailed information is provided for each journal entry line. * Clear Suspense Accounts Examine the General Ledger and account analysis reports to identify the source of entries to the suspense accounts. 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. * Review Detail Account Balances On-line * Review Account Balances via Reports Request accounting reports such as general ledgers. When the balance for group of transactions is zero you can mark the transaction as reconciled. category and date. d) Journal Reports These reports print journal entry batches and include journal entry subtotals. improved online reconciliation reporting. which includes the source. online reconciliation report provides drill-down to underlying sources and source journals for easy identification of reconciliation differences. You can report on foreign currency.13a. trial balances. These reports list beginning and ending account balances and all journal entry lines affecting each account balance. and description. batch name. 14. c) Trial Balance Reports Use trial balance reports to review account balances and activity in summary or detail. a) General Ledger Reports General Ledger Reports facilitate tracing back each transaction to the original source. and descriptions and reference information for each journal entry line. posted. Adjust journals to correct any errors in the journals. Determine the adjusting entries required to net these accounts to zero. * Journal Reconciliation: General Ledger Entry Reconciliation lets you reconcile transactions in GL accounts that should balance to zero. Oracle Financials E-Business Suite Release 12 Period End Procedures 76 . and accounts analysis reports to facilitate reconciliation of Oracle General Ledger with the other Financials and manufacturing modules.

* Check other key system accounts have not been transacted by ad-hoc journals. This operation can be performed across ledgers provided ‘Data Access Set’ grants access. or ‘permanently closed’. The period can be ‘soft closed’. Creditors Control. With a data access set across ledgers programs can be run for multiple ledgers from a single responsibility. for example.Attention: If suspense accounting is not allowed. Any Journals entered into this period while it had a status of Future Enterable. Choose status ‘Open’ to open a new accounting period. Enter Adjustments and / or Accruals and Post To correct errors in account balances made by posting incorrect journals. Generate and post reversal journals that were entered in the prior period. This step will need to be repeated for each ledger unless a data access set is setup to give access to multiple ledgers. For more information please refer to Oracle General Ledger User guide. Attention: The details of posted journals cannot be changed. 18. Oracle Financials E-Business Suite Release 12 Period End Procedures 77 . Intercompany accounts. and manual accruals can be entered into Oracle General Ledger at this point also. can now be posted as the period now has a status of Open. if later adjustments to the balances for that period may be applicable. Open the Next Oracle General Ledger Period Open the next General Ledger accounting period in the Open and Close Periods window. 15. create and post adjusting and reversing journals. Other journal entry adjustments. For example any Oracle Purchasing receipted accruals and manual accruals. * Reconcile Subsidiary Ledgers Identify differences between subsidiary ledgers and the General Ledger. which means that the period cannot be re-opened in the future. Debtors Control. This is controlled by GL: Data Access Set profile option. This step will need to be repeated for each ledger unless a data access set is setup to give access to multiple ledgers. etc. Oracle General Ledger will not post out-of-balance batches. or to re-open a previously soft closed period to enable adjustments to be made. Close the Current Oracle General Ledger Period Close the current GL accounting period in the Open and Close Periods window. for example. except to mark or unmark for reversal. write-offs (refer Accrual Write-Off Report). 16. 17. Determine which differences are errors requiring adjustment to the General Ledger. An incorrectly entered posted journal must be reversed to back-out the accounting of the original posted journal. Perform Final Adjustments Enter and Post any final adjustments as required by the organization.

Run final Financial Statement Generator Reports (FSG) or Report Sets as required by the organization including Income Statements and Balance Sheets. 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. 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 21. 20. or to a separate budget to identify between current year and carry forward amounts if required. which is required to be reported to the relevant Tax Authority. Oracle Payables. including Carry Forward. * Carry forward the funds available as at the end of the year. The Financial Tax Register uses this data to generate Tax Register reports using the Rxi reporting tool. * Carry forward budgets into the current appropriation budget. 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. and export the data to a tab delimited or HTML file. Other facilities available: * Use mass allocations to bring forward part of the funds available. The Financial Tax Register can be used to view the output from the Tax Reporting Ledger using Reports Exchange and Application Desktop Integrator (ADI). To perform Encumbrance year-end procedures. 19. publish the report in different formats.This is controlled by GL: Data Access Set profile option. Mass budget processing also allows you to combine these budgets. and the encumbered budget. Using these products you can change the layout of the report. The Tax Reporting Ledger consists of accounting information created in Oracle Receivables. Run Reports for Tax Reporting Purposes (Optional) A variety of standard reports can be used to provide tax information. With a data access set across ledgers programs can be run for multiple ledgers from a single responsibility. including withholding tax. and Oracle General Ledger. * Carry forward encumbrances. FSGs can also be published via the Application Desktop Integrator (ADI). you must complete each of the following steps: Oracle Financials E-Business Suite Release 12 Period End Procedures 78 . The carry forward process enables managers to perform any of the following: * Carry forward encumbrances for existing transactions (purchases/requisitions). Run Financial Reports for the Closed Period Run a final Trial Balance Report.

Verify that the next year budget figures have been entered.This rule enables you to select Encumbrances Only. * From/To Budget and Budget Organization. Obligation etc. c) Run Year End Carry Forward 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.e. you can select a wide range of criteria for carrying forward balances: * Carry Forward Rule . Define Summary Accounts. Encumbrances and the Encumbered Budget. Oracle Financials E-Business Suite Release 12 Period End Procedures 79 . If you define a new budget for the purposes of the next year budgetary control. Commitment. where you have attached the funding budget to defined account ranges within this form. or select the encumbrance type that you require i. b) Open the next budget year Use the Define Budget window to define a budget for the next budget period. or Funds Available as the basis for the Carry forward * Encumbrance Type . where summary templates are used as the basis for the budgetary control procedures.a) Open the next encumbrance year Use the Open and Close Periods window to open the next encumbrance year.Select the budgets where they are different * Accounting Flexfield Ranges .Select the range of relevant accounting flexfields to be carried forward. you may also need to update the following: Define Budget Organizations.Select ‘All’ for all encumbrances. 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.

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

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

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

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

Perform Encumbrance Year End Procedures (Optional) 15. Cash Management 5. Projects 3. Receivables 7. Run Archive and Purge programs (Optional) 12. Treasury 11. 9. General Ledger 20. Inventory / Cost Management. Order Management 4.2. Purchasing 8. Run Reports for Tax Reporting Purposes (Optional) 21. Payables 6. Purge Transactions (Optional) 19. Assets 10. Archive and Purge Transactions (Optional) Oracle Financials E-Business Suite Release 12 Period End Procedures 84 .

Appendix: More Information Related Metalink Information The following Metalink Information can be reviewed for additional information on period end procedures.1 728871.1 436128.1 Release 12? Oracle Financials Release 12 Period End Procedures 85 .7:00 pm MDT (Conf. Period Close and Trial Balance 'How To' documents R12 SLA: New R12 Payables Trial Balance -. Key: R12) November 19 SLA: Troubleshooting the AP TO GL Reconciliation Subledger Accounting (SLA): FAQ for Support Engineers 749679.1 743390. 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 751830.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 .4 Reconciliation Reports On Standard Cash Receipt.1 740297.1 604739.1 579836.1 558421.1 732928.1 579631.1 579373.1 761502.1 735522. Document Title Doc ID AR: What are the recommended patches for AR-GL Posting.1 437422.1 759002.1 What Is The Period Close Process For Oracle Assets In 557948. Reconciliation and Data Integrity Issues? 'FAQs' for Period Close and Unaccounted Transactions topic in Oracle Payables GL_DATE Difference On R12.0.1 605707. GL Transfer.1 Useful Articles for R12 General Ledger Support Engineers 369993.

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

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->