← Back to Engagement Library

Pentel — Post-Implementation Diagnostics, Reconciliation & Oracle EBS Support

ClientPentel of America
IndustryManufacturing — Stationery & Writing Instruments
Oracle VersionOracle E-Business Suite R12
Modules AP AR GL FA
Engagement Period2010 – 2012
Project TypePost-Implementation Support — Diagnostics & Reconciliation
ComplexityMedium · 447 Files · 15 Work Streams · Diagnostics Focus

Executive Summary

Pentel of America — the US subsidiary of Pentel Co., Ltd., Japan's leading manufacturer of pens, pencils, and art supplies — engaged William Delaney Consulting for post-implementation support of its Oracle EBS R12 environment. The engagement focused on diagnostics, financial reconciliation, and targeted remediation across AP, AR, GL, and FA — addressing issues that had accumulated following the initial Oracle implementation and had not been systematically resolved.

Post-implementation support engagements of this type are distinct from initial implementations: the system is live and business-critical, users are dependent on it, and problems must be diagnosed and resolved without disrupting ongoing operations. The diagnostic skill set — identifying root causes of Oracle system behavior from audit trails, journal entries, subledger records, and configuration settings — is different from the configuration skill set used during implementation.

The 15-work-stream structure and 447 files document a substantive engagement that addressed issues across multiple modules and required detailed reconciliation work to bring Oracle financial records into alignment with business expectations and supporting documentation.

Engagement Context

Pentel of America's Oracle EBS environment, as the US subsidiary of a Japanese parent, carried the additional complexity of intercompany accounting with the Japanese parent entity, transfer pricing for intercompany inventory purchases, and reporting requirements that bridged US GAAP (for US reporting) and Japanese GAAP / IFRS considerations for parent company consolidation. These dimensions add layers of complexity to standard Oracle Financials diagnostics.

Manufacturing subsidiaries of foreign parent companies commonly experience Oracle implementation challenges in areas that pure domestic implementations do not face: intercompany AR/AP matching, foreign currency revaluation at period end, and intercompany elimination entries that must reconcile across two ERP systems with different data models. Diagnosing discrepancies in these areas requires understanding not just Oracle's behavior but also the parent company's accounting expectations.

Oracle Diagnostic & Support Scope

Financial Reconciliation

A systematic reconciliation of Oracle subledger balances to GL was conducted across AP, AR, and FA. Subledger-to-GL reconciliation identifies cases where transactions posted in a subledger did not transfer correctly to the GL — a common post-implementation issue caused by interface errors, posting failures, or accounting rule misconfigurations that were not caught during go-live testing.

AP Diagnostics

AP diagnostics focused on: payment reconciliation (payments posted in Oracle not matching bank statements), invoice holds analysis (invoices on hold beyond acceptable aging), and supplier balance discrepancies (Oracle supplier balance not matching supplier statements). Each diagnostic category followed a structured investigation protocol — query the data, identify the pattern, trace to root cause, document the resolution.

AR Reconciliation

AR reconciliation addressed customer balance discrepancies, unapplied cash (receipts received but not applied to invoices), and aging report accuracy. Unapplied cash is a common AR issue in Oracle implementations where the cash application process was not fully configured or where automatic receipt application rules were not set up correctly during implementation.

FA Validation

Fixed asset validation confirmed that asset depreciation calculations were correct, that assets were assigned to the correct depreciation books, and that the FA subledger balance reconciled to the GL fixed asset accounts. Any discrepancy between FA subledger and GL indicated either an incorrectly processed asset transaction or an accounting rule misconfiguration.

Key Deliverables

DeliverableTypePurpose
Diagnostic Assessment ReportAnalysisSummary of issues identified across AP, AR, GL, and FA with root cause analysis and remediation priority ranking
Subledger-to-GL ReconciliationReconciliationAP, AR, and FA subledger balance reconciliation to GL with discrepancy identification and resolution
AP Issue Resolution LogIssue TrackingItemized log of AP issues (payment reconciliation, holds, supplier balance discrepancies) with resolution documentation
AR Unapplied Cash AnalysisAnalysisIdentification of unapplied cash receipts with recommended application or write-off approach
FA Depreciation ValidationValidationAsset-by-asset depreciation calculation review confirming accuracy of Oracle FA calculations against expected amounts
Configuration Remediation GuideConfiguration DocumentOracle configuration changes required to prevent recurrence of identified issues

Consultant Insights

On Post-Implementation Diagnostics: The most valuable diagnostic skill in Oracle EBS support is the ability to read Oracle's audit trails — AP_ACCOUNTING_EVENTS, XLA_AE_HEADERS/LINES in R12, GL_JE_LINES — to trace a financial transaction from its source (invoice, receipt, payment) through subledger accounting to the GL journal entry. This trace reveals exactly where a discrepancy originated and what configuration or process caused it.
On Unapplied Cash: Unapplied cash balances in Oracle AR are almost always a combination of two causes: (1) the auto-receipt application rules were not configured correctly during implementation, and (2) the AR team does not have a daily process for reviewing and applying receipts that AutoCash could not match. Both the configuration and the process must be fixed — fixing only one will cause the problem to recur.
On Subledger-to-GL Reconciliation: In Oracle R12, the subledger accounting architecture (SLA/XLA) creates a more robust audit trail than Oracle 11i, but it also creates more complexity in reconciliation. The reconciliation path in R12 goes: source document (invoice/payment/receipt) → XLA accounting event → GL journal import. Any break in this chain produces a discrepancy. Understanding the R12 SLA architecture is prerequisite knowledge for effective post-implementation diagnostics.

Reusable Patterns

Lessons Learned

AreaLessonApply On Next Engagement
Unapplied CashUnapplied cash requires both configuration fix and process fix — either alone will allow the problem to recurDeliver both AutoCash configuration update and AR team daily review procedure as paired remediation deliverables
Diagnostics SkillPost-implementation support requires audit trail reading skills distinct from implementation configuration skillsAssess diagnostic capability (XLA/SLA audit trail analysis) when staffing post-implementation support engagements

Related Engagements