| Client | MidAmerican Energy Company |
| Industry | Energy & Utilities — Regulated Electric & Gas |
| Oracle Version | Oracle E-Business Suite R12 |
| Modules | GL AP AR FA CM |
| Engagement Period | 2008 – 2010 |
| Project Type | Oracle Financials Implementation — Regulated Utility with REI Integration |
| Complexity | Medium-High · Regulatory Accounting · REI Data · 935 Files · 8 Work Streams |
MidAmerican Energy Company — a Berkshire Hathaway-owned regulated electric and natural gas utility serving Iowa and surrounding states — implemented Oracle EBS R12 Financials to modernize its financial reporting and operational accounting infrastructure. The engagement covered the full Oracle Financials suite (GL, AP, AR, FA, CM) with the added complexity of regulated utility accounting requirements and an integration with REI (Renewable Energy Integration) data systems supporting MidAmerican's substantial wind energy portfolio.
Regulated utilities operate under a fundamentally different accounting framework than commercial enterprises: rate-based accounting, FERC (Federal Energy Regulatory Commission) reporting requirements, and the need to segregate regulated from unregulated assets and revenues add layers of complexity that standard Oracle Financials implementations do not encounter. The chart of accounts and financial reporting structure must satisfy both GAAP financial reporting and FERC regulatory filing requirements simultaneously.
The 935-file documentation volume across 8 work streams reflects an engagement of substantial depth — particularly in the GL and FA modules where utility-specific accounting treatments required extensive custom configuration and validation against regulatory requirements before go-live approval could be obtained from compliance stakeholders.
MidAmerican Energy's Berkshire Hathaway ownership gave it unusual financial stability for a regulated utility but also brought Berkshire-level financial reporting expectations — precise, clean, and audit-ready. The Oracle implementation needed to produce financial statements that satisfied not only standard GAAP requirements but also Berkshire's internal reporting standards and the FERC Uniform System of Accounts (USofA), which mandates specific account coding for all regulated utility transactions.
The renewable energy dimension was significant: MidAmerican was one of the largest wind energy operators in the US by the late 2000s, with billions in wind energy capital assets. The REI data integration connected Oracle FA to wind farm operational and financial data, ensuring that capital additions, depreciation, and production tax credit calculations aligned with both Oracle's asset accounting and the wind farm management system's operational records.
The .apf, .apj, and .DIS file formats in the project documentation suggest Oracle Financials Analyzer (OFA) and Oracle Discoverer outputs — the BI reporting tools of the R12 era — indicating that financial reporting and analytical capability were a significant deliverable alongside the core module implementations.
The GL chart of accounts was designed to satisfy the dual requirement of GAAP financial reporting and FERC Uniform System of Accounts compliance. The FERC USofA prescribes specific account numbers for regulated utility transactions — plant accounts (100–399), operating expense accounts (400–599), and income accounts (600–699) — that must be mapped to Oracle's flexible segment structure. The chart of accounts design required close collaboration with the regulatory accounting team to ensure every FERC account was properly represented and cross-referenced to the GAAP reporting hierarchy.
Regulated utility fixed assets are accounted for under the FERC plant accounting rules, which differ from standard GAAP depreciation in significant ways: depreciation rates are set by regulatory order (not management estimate), retirements must be tracked at the individual unit level, and the cost of removal must be accrued separately from asset depreciation. Oracle FA was configured to accommodate these requirements through custom depreciation methods, unit-of-property tracking, and cost-of-removal accrual setups.
The REI integration connected Oracle FA mass additions to the wind farm management system — capital additions approved in the REI system triggered Oracle FA mass addition records, ensuring consistent asset capitalization timing between operational and financial systems.
AP was configured for the utility's vendor payment cycles — construction contractors, fuel suppliers, and O&M service providers each with distinct payment terms and bank account routing. Cash Management supported daily bank reconciliation across the utility's treasury accounts, with automated matching rates improved by configuring Oracle's bank statement tolerance rules.
AR supported customer billing for electric and gas service — including consolidated billing for commercial and industrial accounts — alongside billing for wholesale energy sales to other utilities and power marketers. Customer account setup and aging configurations reflected the utility's customer service policies and regulatory requirements for disconnection and collection activity.
| Deliverable | Type | Purpose |
|---|---|---|
| FERC-Aligned Chart of Accounts Design | Architecture / Configuration | GL segment structure mapping FERC USofA account requirements to Oracle's flexible chart of accounts |
| Regulated Plant Accounting Configuration | Configuration Document | Oracle FA setup for FERC plant accounts, regulatory depreciation rates, unit-of-property tracking |
| REI Integration Design | Integration Document | Wind farm capital additions data flow from REI system to Oracle FA mass additions interface |
| AP Payment Cycle Documentation | Process Documentation | Vendor payment batch procedures by payment category (construction, fuel, O&M) with bank account routing |
| Financial Reporting Specifications | Reporting | Oracle Financials Analyzer and Discoverer report specifications for GAAP and FERC reporting requirements |
| Cash Management Configuration | Configuration Document | Bank statement import setup, automated matching rules, and reconciliation exception procedures |
| Period-End Close Procedures | Process Documentation | Regulatory-sensitive period-end sequence with FERC filing deadline alignment |
The FERC chart of accounts requirement drove the GL segment structure design. Oracle's flexible chart of accounts uses a segment combination to represent each accounting code — for MidAmerican, segments were designed to capture: FERC account number, company/entity, cost center, and project identifier. The FERC account number segment was constrained to the FERC USofA account list to prevent non-compliant account coding at transaction entry.
The REI integration used Oracle's standard FA Mass Additions interface table as the target: REI system capital addition records were transformed and loaded into FA_MASS_ADDITIONS, reviewed in Oracle's Mass Additions workbench by the asset accounting team, and posted to the asset register after review. This approach maintained Oracle FA as the system of record while REI remained the operational system, with a clear data handoff point at the mass additions interface.
The FERC Uniform System of Accounts and GAAP do not have a one-to-one mapping — some FERC accounts aggregate what GAAP separates, and vice versa. The chart of accounts design had to satisfy both simultaneously. Resolution was a mapping matrix document that showed, for every Oracle GL account combination, the corresponding FERC account and GAAP classification — reviewed and approved by both regulatory accounting and financial reporting teams before configuration began.
Oracle FA's depreciation rate configuration does not natively track the regulatory order authority behind each rate. When rates change by regulatory order, there is no Oracle-native audit trail connecting the rate change to the authorizing order. Resolution was a custom depreciation rate log table that captured every rate change with the regulatory order reference, effective date, and approver — maintained alongside the Oracle FA configuration as a regulatory compliance record.
MidAmerican's wind energy capital program generated high volumes of mass addition records — individual turbine components, foundation structures, electrical interconnections — each requiring classification into the correct FERC plant account. Manual review of this volume in Oracle's Mass Additions workbench was not practical. Resolution was a pre-classification rule engine applied during the REI-to-Oracle interface that auto-classified the majority of additions by component type, leaving only exceptions (multi-category components, cost allocations) for manual workbench review.
The existing asset register contained decades of regulated plant data in legacy formats (.apf, .apj file types suggest Oracle Financials Analyzer or legacy Oracle formats) requiring transformation before Oracle FA import. The migration effort was extensive, requiring a dedicated data cleanse workstream to standardize FERC account assignments, normalize asset descriptions, and validate depreciation calculation continuity from the legacy system to Oracle.
| Area | Lesson | Apply On Next Engagement |
|---|---|---|
| Regulatory Expertise | Oracle expertise alone is insufficient for regulated utility implementations — regulatory accounting knowledge is required on the team | Include utility regulatory accounting SME as a mandatory team role for any regulated utility engagement |
| FA Volume | Large capital programs generate mass addition volumes that exceed manual workbench capacity — pre-classification is required | Assess mass addition volume in week 1; if >200 additions/period, plan for automated pre-classification |
| Depreciation Governance | Oracle does not natively track the regulatory authority behind depreciation rate decisions — custom audit log required | Build depreciation rate change log into FA implementation scope for all regulated utility engagements |
| Legacy Migration | Decades-old regulated plant data requires extensive cleanse before Oracle FA import — scope the cleanse from a data sample, not assumptions | Sample 5% of legacy asset records in week 1 to identify data quality issues and size the cleanse effort |