The Oracle EBS Close & Reconcile Kit
Why the period won't close, the procedure to close it, and the templates to prove the numbers.
3 PDFs + Excel110 pages11 templatesR12.1 / R12.2
Email me the guide- The close that should take five days takes ten, and the last three are firefighting.
- Close Period fails with one error message, and the real cause is somewhere in eight subledgers.
- One person owns the reconciliations, and the timeline is their calendar.
- Every month it’s the same conditions — unvalidated invoices, XLA errors, an unposted batch — discovered at nine on the last night.
The Period Close Diagnostic Handbook
33 pagesWhy the period won’t close, in which module, and the exact concurrent program that clears it.
Part One — Why closes run long
- The Five Bottlenecks
- Compressing the Cycle
- The Close Dependency Chain
Part Two — The blocking conditions, module by module
- Payables
- General Ledger
- The Other Six Subledgers
- Reading a Readiness Report
- The Conditions That Recur
Part Three — Running it as a process
- The Day-Minus-3 Scan
- Measuring the Close
Appendices
- The Close Readiness Checklist
- Concurrent Program Reference
- Table Reference
The Period Close Procedures Manual
40 pagesWhat to do, in what order, and who owns each step — module by module.
Part One — Governing the close
- Close Order and Dependencies
- The Cutoff Schedule
- The Integrated Close Calendar
Part Two — Module procedures
- Payables
- Purchasing
- Inventory
- Receivables
- Fixed Assets
- Projects
- General Ledger
Part Three — When it doesn’t go to plan
- Troubleshooting
- What Changed: 11i to R12 to 12.2
Appendices
- Master Close Checklist
- Cutoff Schedule Template
- Key Account Reconciliation Register
The Reconciliation Workbook
37 pagesProving the subledgers agree with the ledger once the close is done.
Part One — Method
- The Universal Method
- Investigating a Variance
- Sign and Date Discipline
Part Two — The reconciliations
- Payables to General Ledger
- Receivables to the Aging
- Receivables to General Ledger
- Purchasing Accrual to General Ledger
- Inventory to General Ledger
- Assets to General Ledger
- Cash, Projects and Tax
Part Three — Correction and prevention
- Where Corrections Belong
- Preventing the Recurrence
Appendices
- Reconciliation Control Sheet
- Variance Cause Index
- Report Parameter Discipline
The Reconciliation Template Set
11 tabsThe Excel workbook the Reconciliation Workbook is built around.
READMEAP to GLAR to AgingAR to GLPO AccrualInventoryAssetsCashReconciling ItemsControl SheetVariance Index
- Run the day-minus-3 readiness scan and walk into close week with a work list instead of a surprise.
- Re-sequence the close so independent tasks run in parallel — the single biggest, cheapest compression available.
- Name the exact concurrent program that clears each blocking condition, module by module.
- Publish a cutoff schedule with named owners that people actually follow.
- Prove AP, AR, PO accrual, Inventory, Assets and Cash tie to the ledger, with a sign-and-date record an auditor accepts.
- Track the four close KPIs that show whether any of it is working.
The Five Bottlenecks
Five causes account for most close overrun. Only two of them are technical.
| Bottleneck | What it looks like | Typical cost |
|---|---|---|
| Sequential processing where parallel is possible | Independent tasks run one after another — Receivables revenue recognition, then AP accruals, then Fixed Asset depreciation, when all three have no dependency on each other | 2–4 days |
| Subledger accounting transfer failures | Create Accounting failing on invalid account combinations, missing event class assignments, volume-related degradation, or JVM memory allocation | 4–8 hours per failure-and-restart cycle |
| Concurrent manager resource contention | Demand spikes at close; critical programs compete with routine processing | 30–60+ minutes wait per submission at peak |
| Manual reconciliation dependencies | Critical reconciliations owned by one person, whose availability determines the timeline | 1–2 days when that person is unavailable |
| GL posting and period close sequencing | Final steps delayed by upstream issues nobody detected earlier; posting failures discovered at the worst moment | 1–3 days |
From the Diagnostic Handbook, Chapter One.
William A. Green has spent 27 years inside Oracle E-Business Suite Financials — as a former Oracle employee, as a functional and technical lead on more than 35 implementations, and for six years at Rimini Street supporting Fortune 500 EBS clients on releases Oracle had stopped patching. He writes fixes for a living. This guide is the part of that work that fits in a PDF.