How a Hospital Group Cut Its Oracle EBS Month-End Close from 12 Days to 6
A slow close is usually a system problem, not a people problem. An Oracle EBS health check uncovered the bottlenecks behind one hospital group's month-end close and the fixes that cut the cycle in half.
Client: Anonymized multi-specialty hospital group with several
branches
Platform: Oracle E-Business Suite R12.2
Modules: GL, AP, AR, Fixed Assets, Inventory and Purchasing
Integration: Hospital Information System (HIS) to Oracle EBS
Service: Oracle EBS health check and performance tuning
The challenge
Every day, the group's branches sent thousands of outpatient and inpatient billing entries, pharmacy sales and diagnostics from the HIS into Oracle EBS. Insurer claims, supplier invoices and equipment additions arrived at the same time, with much of the activity landing in the last week of the month.
Leadership considered adding finance headcount, while the finance team suspected a system bottleneck. Their day-to-day symptoms included:
- HIS billing loads and accounting programs sitting in Pending status for long stretches.
- Custom revenue and insurer-ageing reports taking hours and often being resubmitted.
- HIS-to-AR and pharmacy stock-to-GL differences surfacing only in the final days.
- No clear view of which delays were driving the close.
Our approach: an Oracle EBS health check
We reviewed concurrent request history, database performance data and reconciliation patterns across several closing cycles, focusing on three areas commonly behind a slow Oracle EBS close.
1. Concurrent program tuning
What we found: Interface loads, Auto Invoice, Create Accounting and Transfer to GL shared the Standard Manager with reports and maintenance jobs. Statistics gathering and purge programs ran during close. New HIS service codes and departments lacked matching EBS setup, causing repeated Auto Invoice failures and manual resubmissions.
What we fixed:
- Created dedicated concurrent manager queues and work shifts for close-critical programs.
- Moved maintenance jobs outside the close window.
- Validated HIS service-code and department mapping before each load.
- Added failure alerts so issues became visible in minutes, not hours.
2. Custom report performance
What we found: The departmental revenue and insurer-ageing report took about four hours. It processed records row by row in PL/SQL, joined accounting tables without selective filters and ran against stale optimizer statistics. The pharmacy stock valuation report scanned every branch in one run.
What we fixed:
- Rewrote the logic as set-based SQL and added a supporting index.
- Refreshed statistics on the affected tables.
- Split reports by branch so they could run in parallel and off-peak.
The longest report dropped from about four hours to about 25 minutes.
3. Subledger-to-GL reconciliation
What we found: Differences were discovered at the end of close, when there was least time to investigate. Common causes included:
- Cancelled bills, refunds and credit notes posted late from the HIS.
- Insurer claim adjustments and write-offs recorded in the final days.
- Pharmacy and consumables inventory valuation not matching the GL.
- Medical equipment placed in service but not capitalized on time.
What we fixed:
- Introduced a daily HIS-to-AR control-total check.
- Set up weekly subledger-to-GL reconciliation with exception reports for unaccounted and errored transactions.
- Added an asset capitalization checkpoint to the close calendar.
- Assigned a named owner for each module and branch.
Results after two closing cycles
Reconciliation differences were found earlier in the cycle. Close overtime dropped, management reports reached leadership sooner and the headcount plan was shelved.
Frequently asked questions
Why is month-end close slow in Oracle EBS?
Common causes include queued or failing concurrent programs, custom reports that run for hours and subledger differences found late in the close.
What does an Oracle EBS health check include?
It reviews concurrent processing, custom report performance and subledger-to-GL reconciliation, then produces a prioritized list of fixes.
Does the review cover our Hospital Information System interface?
Yes. Mapping and timing issues between the HIS and Oracle EBS often delay close, so the interface is part of the review.
Is your month-end close taking too long?
Tell us about your close cycle. We will review concurrent programs, custom reports and subledger reconciliation, then send you a clear list of what to fix first.
Talk to our Oracle EBS team