Oracle Month-End Close Checklist

A step-by-step Oracle Fusion Cloud and EBS month-end close checklist covering period open/close, Create Accounting, sub-ledger transfer, GL reconciliation, revaluation, and financial reporting. Built for Oracle GL administrators, AP/AR managers, and controllers.

Free download Excel, Word & PDF 28+ Oracle close tasks
GL
AP
AR
+
Used by 1,800+ Oracle finance teams
Oracle Month-End Close
Pre-Close (Day 1)
Open GL period in Oracle
Post final AP invoices
Sub-Ledger Transfer (Days 2-3)
Run Create Accounting for all sub-ledgers
Transfer journals to General Ledger
GL Close (Days 3-4)
Execute revaluation and translation
Reconcile GL to sub-ledger totals
Reporting (Day 5)
Generate FSG financial reports
Close GL period
25% Complete — 2 of 8 tasks done

Build your Oracle month-end close checklist

Check off tasks, assign owners, and track your Oracle close progress in real time.

1

Pre-Close Preparation (Day 1)

Open new GL period in Oracle General Ledger
Verify sub-ledger periods are open (AP, AR, FA, Projects)
Post final AP invoices and process payment batches
Complete AR receipt application and clear unapplied receipts
Notify business units of cut-off deadlines
Post accrual and deferral journal entries
Review and approve pending journal batches
2

Sub-Ledger Transfer (Days 2-3)

Run Create Accounting for Payables
Run Create Accounting for Receivables
Run Create Accounting for Fixed Assets
Transfer sub-ledger journals to General Ledger
Run asset depreciation for the period
Reconcile bank statements via Cash Management
Review SLA accounting event errors and resolve
3

GL Close (Days 3-4)

Run foreign currency revaluation
Execute currency translation for reporting currencies
Post intercompany eliminations
Reconcile GL balances to sub-ledger totals
Review and post manual adjusting journal entries
Run allocations for shared cost centers
Verify all journal imports posted successfully
4

Reporting and Period Close (Day 5)

Generate trial balance using FSG or Financial Reporting
Run P&L and balance sheet reports
Perform flux analysis on material account variances
Prepare management reporting package
Review intercompany balances with counterparts
Obtain sign-off from finance leadership
Close GL period and lock for all ledgers
Live preview
Oracle Month-End Close
Reporting Period:
0
Done
28
Pending
28
Total

How to close the books in Oracle in four steps

1

Open and prepare

Open the new GL period, verify sub-ledger periods are open, post final AP invoices and AR receipts, and enter all accruals and deferrals before the cut-off deadline.

2

Transfer sub-ledgers

Run Create Accounting for Payables, Receivables, and Fixed Assets. Transfer all sub-ledger journals to the General Ledger and resolve any SLA accounting event errors.

3

Close the General Ledger

Execute foreign currency revaluation and translation, post intercompany eliminations, run cost allocations, and reconcile GL control accounts to sub-ledger totals.

4

Report and close period

Generate the trial balance and financial statements using FSG or Oracle Financial Reporting, run flux analysis, prepare the management package, obtain sign-off, and close the GL period.

Download a ready-to-use Oracle month-end close checklist

Excel (.xlsx)

Editable Oracle close checklist with Create Accounting steps and sub-ledger transfer tracking.

Word (.docx)

Printable Oracle close procedure document with sign-off fields for each phase.

PDF

Print-ready Oracle month-end close checklist formatted for wall charts and team handoffs.

Oracle month-end close timeline, mapped out

A typical Oracle close runs over 5 business days. Here is how the checklist phases map to each stage.

D1
Pre-Close
  • Open GL and sub-ledger periods
  • Post final AP invoices
  • Apply AR receipts
  • Post accruals and deferrals
D2-3
Sub-Ledger
  • Create Accounting (AP, AR, FA)
  • Transfer journals to GL
  • Run asset depreciation
  • Resolve SLA errors
D3-4
GL Close
  • Foreign currency revaluation
  • Currency translation
  • Intercompany eliminations
  • GL-to-sub-ledger reconciliation
D5
Reporting
  • Trial balance (FSG)
  • P&L and balance sheet
  • Flux analysis
  • Close GL period
Pre-CloseSub-LedgerGL CloseReporting

Close faster in Oracle with Bluecopa

Automate reconciliations, streamline journal entries, and cut your Oracle month-end close from 10 days to 4.

Get a Demo →

How Bluecopa accelerates Oracle month-end close

Bluecopa connects directly to Oracle Fusion Cloud and EBS, automating reconciliations, sub-ledger matching, and exception management so your team closes the books faster with fewer manual steps.

1 Native Oracle integration

Connect directly to Oracle Fusion Cloud or EBS. Pull trial balances, sub-ledger journals, and open items without manual CSV exports or BI Publisher reports.

2 Automated reconciliation

Match GL to sub-ledger, intercompany, and bank balances automatically. Bluecopa flags exceptions so you fix issues instead of hunting through Oracle reports.

3 Real-time close tracking

Replace spreadsheet status updates with a live dashboard. See which Create Accounting runs are done, who owns what, and where the close is stuck across all ledgers.

4 Audit-ready documentation

Every reconciliation, journal entry, and sign-off is logged with a timestamp and user trail. External auditors get the evidence they need without chasing people.

Do this, avoid that

✓ Do this

  • ✓ Run Create Accounting for every sub-ledger before transferring journals to the GL
  • ✓ Verify SLA accounting events are error-free before closing any sub-ledger period
  • ✓ Reconcile sub-ledger totals to GL control accounts before running revaluation
  • ✓ Use Oracle's Period Close Exception report to identify unposted or incomplete transactions
  • ✓ Document every manual journal entry with a business justification and supporting attachment
  • ✓ Test revaluation and translation in a sandbox instance before running in production

✕ Avoid that

  • ✕ Closing the GL period before all sub-ledger Create Accounting runs are complete
  • ✕ Transferring journals to GL without resolving SLA accounting event errors first
  • ✕ Running revaluation before the bank reconciliation is finished
  • ✕ Relying on spreadsheets to track close tasks across multiple Oracle ledgers and business units
  • ✕ Skipping the GL-to-sub-ledger reconciliation because the numbers "look right"
  • ✕ Posting adjustments after the period is locked without proper reopening approval

Oracle month-end close terms, explained

GL Period

A time segment in Oracle's accounting calendar that controls when transactions can be posted to the General Ledger. Periods must be explicitly opened and closed by a GL administrator. Oracle supports multiple period statuses: Never Opened, Future Entry, Open, Closed, and Permanently Closed.

Create Accounting

An Oracle process that converts sub-ledger transactions (AP invoices, AR receipts, asset depreciation) into accounting entries using Subledger Accounting (SLA) rules. These entries are then transferred as journal batches to the General Ledger for posting.

Subledger Accounting (SLA)

Oracle's engine for generating accounting entries from sub-ledger transactions based on configurable accounting methods. SLA determines the accounts, amounts, and accounting treatment for every AP, AR, and FA transaction before it reaches the GL.

FSG (Financial Statement Generator)

Oracle's built-in reporting tool for generating financial statements like trial balances, income statements, and balance sheets directly from GL data. In Fusion Cloud, FSG is being replaced by Oracle Financial Reporting Studio (HFR) and OTBI dashboards.

Revaluation

The process of restating foreign-currency-denominated GL balances to the functional currency at the period-end exchange rate. Oracle posts the resulting unrealized gain or loss to a designated revaluation account, required for IFRS and GAAP compliance.

Translation

The process of converting an entire set of financial statements from the functional currency to a reporting currency using period-end, average, or historical exchange rates. Required for consolidated reporting in multinational Oracle deployments.

Frequently asked questions

Oracle month-end close is the process of finalizing all financial transactions for a given period within Oracle Fusion Cloud or EBS. It involves opening and closing GL periods, running Create Accounting to transfer sub-ledger entries (AP, AR, Fixed Assets) to the General Ledger, executing foreign currency revaluation and translation, and generating financial reports using FSG or Oracle Financial Reporting. The goal is to produce accurate financial statements that reflect the company's position at period end.
Most Oracle-based organizations complete their month-end close in 5 to 10 business days. Companies with mature processes and automation tools often close in 3 to 5 days. The timeline depends on the number of ledgers, business units, intercompany transactions, and how much of the close is still manual. Automating the Create Accounting and reconciliation steps typically removes 2 to 3 days from the cycle.
Create Accounting is Oracle's process for converting sub-ledger transactions into accounting entries using Subledger Accounting (SLA) rules. Every AP invoice, AR receipt, and asset depreciation entry must go through Create Accounting before it appears in the GL. If Create Accounting is not run for all sub-ledgers, the GL will be incomplete and the trial balance will not tie to sub-ledger totals. Running it is one of the most critical and often most time-consuming steps in the Oracle close.
The core close steps are the same, but Fusion Cloud simplifies several areas. Create Accounting runs are faster and can be scheduled. The Period Close Dashboard gives real-time visibility into what is open across all sub-ledgers. FSG is being replaced by Oracle Financial Reporting Studio and OTBI for more flexible reporting. Bank reconciliation in Fusion Cloud is more integrated via Cash Management. The biggest operational difference is that Fusion Cloud provides a unified close workspace, while EBS requires navigating multiple responsibility menus.
Intercompany close in Oracle starts with confirming that all intercompany invoices are posted and matched across business units. Oracle Fusion Cloud has an Intercompany module that automates the creation of balancing entries. In EBS, intercompany transactions are typically managed through Global Intercompany System (GIS) or custom interfaces. After matching, any imbalances must be resolved before posting elimination entries. The eliminations are either posted in a consolidation ledger or handled in Oracle Financial Consolidation Hub.
Bluecopa connects directly to Oracle Fusion Cloud and EBS via native integrations and automates the most time-consuming parts of the close: GL-to-sub-ledger reconciliation, bank statement matching, intercompany balance confirmation, and exception management. Instead of manually exporting data from Oracle into spreadsheets, Bluecopa ingests trial balances and transactional data in real time, runs matching rules, and surfaces only the exceptions that need human attention. Teams using Bluecopa with Oracle typically reduce their close cycle by 40 to 60 percent.

Related checklists