1 / 57

MC Finance Integration

MC Finance Integration. March 10, 2010 Design Workshop. Agenda & Schedule. Agenda for Session 1 - Summary. Scope Phase 0 Architecture Phase 1 Architecture Phase 0 Recommendation Phase 1 – Key decisions Phase 1 – Timeline 2011 Transitions …

wynona
Download Presentation

MC Finance Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MC Finance Integration March 10, 2010 Design Workshop

  2. Agenda & Schedule

  3. Agenda for Session 1 - Summary • Scope • Phase 0 Architecture • Phase 1 Architecture • Phase 0 Recommendation • Phase 1 – Key decisions • Phase 1 – Timeline • 2011 Transitions … • When legal entities are expected to be consolidated • When payrolls are expected to be consolidated • RICE List

  4. Project Summary

  5. Phase 0 - Recommendation

  6. Summary of Recommendations for Financial Integration – Phase 1 • Business Group • The recommendation is to have one business group which will house employees from both BCG and RCG. This helps in quickly adapting to the new organization structure. • Set of Books • The recommendation is to have one set of books. The set of books can house multiple legal entities thus meeting the statutory requirement and at the same time minimizing the burden of maintaining multiple set of books. • Operating Unit • The recommendation is to have one operating unit. This provides the capability to easily integrate financial functions in the short term and supply chain functions in the long term. • Reporting Tools • Spreadsheet Server primarily; Business Intelligence to follow

  7. Summary of Recommendations for Financial Integration – Phase 1 • Legal Entities (Modeled by Company Segment in Chart of Accounts) • We will add company values for RCG LLC, Store Support and potentially a separate company value for Store Support Canada. This needs to be confirmed. • COA Structure in Peoplesoft • The recommendation is continue the current JDE COA for 2010. The feeds (payroll and garnishments) will be mapped to MC COA using the mapping utility. • For 2011 and beyond, feeds (payroll and garnishments) from Peoplesoft should reflect EBS COA. HR/Payroll team target end of 2010 for consolidated payroll for MC. • COA Structure in Legacy (R6000 and 7i). • The recommendation is continue the current legacy COA in 2010. The journals will be mapped to the MC COA using the COA mapping utility. • For 2011 and beyond, consider a Phase 2 to replace RCG COA in legacy with EBS COA. The effort to do this is being assessed. This could be performed in parallel with payroll consolidation and standardization of departments across systems (EBS, RS6000, PeopleSoft, etc) within Masco Cabinetry.

  8. Phase 1 – Implementation Strategy • Phase 1 timeline is independent of the timeline to relocate the finance department into a new HQ location • For Phase 1 go-live and operation – we expect to have 1 logical finance department operating out of 2 physical locations (Adrian and Middlefield) • Finance team (in Middlefield) would be trained on Oracle EBS, so they can function in their roles • With Phase 1 implementation, there will be a single close process. Training across the finance function (both Adrian and Middlefield) will be required to make this successful.

  9. Transition Tasks for 2011 (upon legal entity consolidation) • Retire selected “company” values in MC COA • COA mapping from RCG to MC COA to reflect mapping to active “company” values • Purchasing/Receiving: update configurations to reflect active “company” values • iExpense: Consolidate T&E templates to reflect operational “company” values • Fixed Assets – Mass Update to reflect updated “company” values • Payables – SLA for accounting by company will no longer be required

  10. Draft RICE List Part 1/2

  11. Draft RICE List Part 2/2

  12. Major Design Tasks • Functional Specifications for RICE - ~500 - 600 hours • COA Mapping ~ 120 hours • Document procedure for creating each journal for closing (~300 manual journals) • Training for RCG team on Oracle

  13. Summary Timeline for Phase 1

  14. Some concerns • Have we understood all reporting requirements • Significant RICE for Phase 1 • Forecast Vs Budget • Finance resource availability – co-locate to speed up decision making

  15. Phase 2 – for January 2011 Standardize use of MC COA across MC systems: • Oracle EBS – consolidate and standardize list of values for each MC COA segment • Department (major effort) • Product • LOB • Market (consistency in level of detail) • PeopleSoft – in conjunction with consolidating payroll for Jan 2011, map payroll directly to MC COA (eliminate intermediate mappings to old BCG COA and RCG COA) • Legacy (RS6000 and other legacy applications) • Push down MC COA so COA mapping can be eliminated • Replace monthly semi-manual journals with automated daily integration to GL

  16. Agenda for Session 2 - EBS Structure Decisions • Business Group and Employee Data, • RCG Legal Entities (Company Segment), • Structure for US and International Operations

  17. Business Group, Ledger, OU and Inv Org

  18. Business Group and Employee Feed from Peoplesoft

  19. Oracle EBS Chart of Accounts – Company Segment

  20. Oracle EBS Chart of Accounts – Company Segment

  21. Alternative Structure – Not Recommended

  22. Oracle Structures for US Operations

  23. Oracle Structures for International Operations (Canada)

  24. Oracle Structures for International Operations - Contd

  25. Agenda for Session 3 – COA Mapping and Reporting • EBS and RCG COA Mapping Strategy, • Advanced Cost Accounting , • Reporting

  26. MC COA and RCG COA/ACA – Mapping Strategy

  27. Map COA or replace RCG COA in Legacy (RS6000)

  28. Advanced Cost Accounting

  29. Reporting to Support Finance and Plants

  30. Reporting to Support Finance and Plants

  31. GL Conversion (Budget and History)

  32. Agenda for Session 4 – AP & Procurement • AP/PO by Legal Entity, • Procure to Pay Conversion Strategy, • Procurement Card Process, • Receipt Correction Process. • Procurement Scope: • Fixed Assets across the enterprise • Expense purchasing for HQ(s) only

  33. AP/PO by Legal Entity until Legal Entity Consolidation

  34. Procure to Pay Conversion Strategy

  35. Procure to Pay Conversion Strategy - Contd

  36. Procurement Card Process

  37. Receipt/PO Correction Process

  38. Procurement Scope (Dana Bilski) • Fixed Assets across the enterprise • Expense purchases for HQ(s) • Plant MRO purchases will stay on 7i

  39. Agenda for Session 5 – iExpense & Payroll • iExpense • Payroll • Garnishments

  40. BCG Current Process for Employee Expense

  41. RCG Current Process for Employee Expense

  42. Expense Report Process Comparison

  43. Future Process for Employee Expense

  44. iExpense Implementation

  45. Finance Integration Needs from HR/Payroll – Garnishments

  46. Finance Integration Needs from HR/Payroll – Garnishments

  47. Finance Integration Needs from HR – Payroll

  48. Finance Integration Needs from HR/Payroll – Payroll

More Related