# Oracle EBS Month-End Close Checklist: GL, AP, AR

> Source: https://netray.co/erp-help/ebs-month-end-close-checklist-gl-ap-ar
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

Close sub-ledgers before General Ledger: finish and account for all Payables and Receivables transactions, close the AP and AR periods, transfer journals to GL through Create Accounting, reconcile sub-ledger to GL, then close the GL period last. Closing GL before a sub-ledger is fully accounted is the single most common cause of a reopen.

## Kind

how-to

## System

oracle-ebs

## Erp

Oracle E-Business Suite (EBS)

## Module

General Ledger / Payables / Receivables

## Query

oracle ebs month end close checklist gl ap ar

## Alternate Queries

- how to close month end in oracle ebs
- EBS period close order AP AR GL
- oracle ebs close accounting period steps
- what order do you close periods in EBS

## Applies To

EBS 12.1.3 and 12.2.x with Subledger Accounting (SLA)

## Steps

### Standard EBS close sequence

**Items:**

Confirm all Purchasing receipts, AP invoices, and AR transactions for the period are entered - late-entered transactions after close force a reopen.

In Payables, run the Payables Period Close Exceptions Report (Payables > Other > Request > Payables Period Close Exceptions Report) to find unaccounted or unposted invoices and payments before you even attempt the close.

Run Create Accounting for Payables (final mode) to account all remaining transactions, then close the AP period in Payables > Setup > Payments > Control Payables Periods (or Accounting > Control Payables Periods, depending on version).

In Receivables, complete AutoInvoice, run Revenue Recognition if used, then Create Accounting in final mode; close the period in Receivables > Control > Accounting > Open/Close Periods.

Close any other feeder sub-ledgers you use - Fixed Assets (run depreciation first) and Inventory/Cost Management - following the same accounted-then-closed pattern.

Transfer subledger journals to GL, either automatically via Create Accounting's Transfer to GL option or manually through the SLA Transfer Journal Entries to GL program, then run Journal Import if any legacy interface feeds are still used.

In General Ledger, review and post all imported journals (Journals > Import), run the Account Analysis or Trial Balance report and compare it to sub-ledger control totals for a reconciliation check.

Only after sub-ledger-to-GL reconciliation ties out, close the GL period in General Ledger > Setup > Open/Close Periods; the next period should already be in Future status so postings do not stall.

## Sections

### Why the order matters

**Body:**

EBS enforces sub-ledger before GL for a structural reason: General Ledger only knows about a transaction once Subledger Accounting has created a journal entry and transferred it across. If you close the GL period while AP or AR still has unaccounted transactions, those transactions cannot post anywhere - they either fail Create Accounting silently or land in the next open GL period, throwing off both months.

The Payables and Receivables period close forms actively check for this and will refuse to close if unaccounted or on-hold transactions exist, which is the correct behavior even though it is often the step that trips up a first-time closer under deadline pressure.

### The unaccounted transactions trap

**Body:**

The most common reason a period will not close is a handful of transactions stuck in Draft or Invalid accounting status - often an invoice with a hold, a credit memo missing a distribution, or a receipt that failed matching. Run the period close exceptions report first rather than attempting the close and reacting to the error, since the report lists every blocking transaction with its ID in one place.

Payment holds and matching holds are a frequent culprit in AP specifically - Create Accounting will account the invoice header but the distribution lines tied to a hold stay unaccounted, and the period close form correctly refuses to proceed until the hold is released or the invoice is cancelled.

### Reconciling sub-ledger to GL before you close GL

**Body:**

Do not treat the GL close as a formality once sub-ledgers are closed - run a reconciliation report (SLA's Account Analysis report, or a custom query comparing sub-ledger control account balances to the GL trial balance) to confirm every journal actually transferred and posted. A journal can sit in the GL interface table unposted because of an invalid account combination or a disabled cross-validation rule, which will not block the sub-ledger close but will leave GL out of balance.

Keep the next accounting period in Future Entry status throughout the close window, not Never Opened, so that any late correcting entry or accrual reversal posts cleanly instead of erroring with a period status message.

**Code:**

- SELECT period_name, closing_status FROM gl_period_statuses WHERE application_id = 101 ORDER BY start_date;

### Handling a period that will not close

**Body:**

If Control Payables Periods reports a nonzero count under Unaccounted or Unvalidated, drill into the Payables Period Close Exceptions Report rather than guessing - it names each invoice, its status, and the specific reason it is blocking close (hold, missing distribution, or pending approval). The same logic applies on the AR side with the Receivables period close exception report for unapplied receipts and incomplete transactions.

For a genuinely stuck transaction that cannot be resolved before the deadline (for example, a dispute pending resolution), the standard workaround is to reverse or write off the specific item rather than force-closing the period, since EBS does not offer a true override once the close validations fail.

## Pitfalls

- Closing GL before confirming every sub-ledger journal actually transferred and posted, not just that the sub-ledger period itself is closed.
- Ignoring holds on AP invoices until close day - matching and payment holds silently keep distributions unaccounted.
- Forgetting to run depreciation before closing the Fixed Assets period, which then blocks the FA-to-GL transfer.
- Leaving the next period as Never Opened, so a late correcting entry after close has nowhere valid to post.
- Running Journal Import without reviewing the import log, missing a batch that rejected on an invalid account combination.
- Treating the close as done once periods show Closed status, without reconciling sub-ledger control totals to the GL trial balance.

## Ai Angle

ERPray grounded on the EBS instance can run the Payables and Receivables period close exception checks on demand and summarize, in plain language, exactly which invoices or receipts are blocking close and why - so the close owner spends the last hour of the month fixing the actual holds instead of re-running exception reports and cross-referencing invoice numbers by hand.

## Faq

### Can I close AP or AR before all invoices for the period are entered?

**Answer:** You can, but any invoice dated in that period entered afterward will land in the next open period instead, which misstates both months unless you manually adjust. Best practice is to hold the sub-ledger close open until AP and AR confirm cutoff, then close on schedule.

### What does Closed Pending status mean in Control Payables Periods?

**Answer:** Closed Pending means the close request was submitted but the concurrent program that sweeps remaining unaccounted transactions has not finished, or found exceptions. Check the concurrent request log and the period close exceptions report rather than resubmitting the close blindly.

### Do I need to close Inventory before or after AP?

**Answer:** There is no hard system dependency between them, but if Inventory costing (especially standard cost variance) feeds GL accounts that AP accruals also touch, close Inventory before running your final AP accrual reconciliation so both sides reflect the same period's activity.

### Why did my GL trial balance not match Payables after both closed cleanly?

**Answer:** A clean sub-ledger close only confirms transactions were accounted, not that the resulting journal successfully posted in GL. Check Journals > Import for a rejected batch, usually from an invalid or disabled account combination that needs correcting before the journal can be resubmitted.

## Search terms

oracle ebs month end close, ebs close AP period, ebs close AR period, ebs close GL period, payables period close exceptions report, ebs subledger accounting transfer to gl, control payables periods form, ebs journal import review, ebs period close order, oracle ebs reconciliation subledger to gl

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json