Breadcrumbs
Home / Blog / Trends & Technology / Going Green in ERPWritten by Helene Abrams Sunday, January 20 2008
Month- and year-end reconciliation of corporate financial data that relies on spreadsheets is a universal practice that is not fun, not accurate, and not necessary. One goal of many companies implementing an ERP system is to eliminate these spreadsheets. However, even with ERP systems in place, most corporations still rely heavily on spreadsheet reconciliation because their implementations sometimes reside in different systems or rely on separate charts of accounts (COAs) for different parts of their businesses. A company having different charts of accounts, for example, has no choice. To provide meaningful information for reconciliation, consolidation, or budgeting, the company must have a consistent representation of the data. Thus, data that was recorded using different categorizations must be ‘translated’ or ‘harmonized’ by spreadsheets that attempt to standardize and make comparable the reports derived from the original data.
Neither the spreadsheet process nor the resources consumed by the spreadsheet effort are trivial. A workflow study done by one of the major accounting firms at a client site found that mid-sized companies used literally thousands of spreadsheets to map transactions between entities, and to reconcile supporting detail to their respective general ledgers. As an ecological matter, eliminating the many copies of those often lengthy printouts would have a favorable “green” impact, but the more obvious “green” impact is financial. In that particular company, over 450 FTE were being devoted to spreadsheet-based reconciliation, consolidation, or budgeting despite the presence of a fully implemented ERP system. The project manager estimated that having a more fully integrated ERP system with standardized charts of accounts would have reduced the spreadsheet headcount by 80%. Although the example at first seems extreme, it is not once the far-flung multi-jurisdictional nature of modern business entities and the familiar growth-by-acquisition patterns are considered. Profitable, growing companies regularly add new pieces to their business and with them heterogeneous data and systems.
Beyond the resources consumed in maintaining a spreadsheet-supported reconciliation process, there are significant business risks that attend the process: simple error and the potential for fraud, misuse, and liabilities that could follow. Focusing on spreadsheet error, data from an independent study show that “one percent of formula cells have errors” (Hesse). Out of eighty-eight spreadsheets audited in seven studies, ninety-four percent of them contained errors. While a single error can make a negative impact, hundreds of errors can lead to disastrous results for an organization. Given the way in which the spreadsheets often build upon one another, one taking data from the other and further analyzing or adjusting it, there easily can be a compounding effect, making an accurate financial or business performance picture much less likely to emerge from the spreadsheet process. Some errors end up being errors of high visibility and great magnitude. In 2003, financial services company Fannie Mae “admitted to making a $1.2 billion error in calculating third quarter earnings on a spreadsheet” (Hesse).
The problem of error, and resultant inaccuracy in spreadsheet compilations, is difficult to address effectively. One common method for detecting and eliminating human error in reporting and data analysis is peer review in the form of having others check the work. While peer-reviews will reduce the number of errors that make it through the mix, in this context errors are likely to persist because of the sheer number of spreadsheets being produced at the desktop level with the possibility of error in virtually every cell, or formula, or input gathered for another spreadsheet. Here too, reducing the need for spreadsheets by standardizing the charts of accounts in the ERP system in a way that corresponds to business operations and reporting needs is a more certain path to eliminating error than improved oversight of the spreadsheet process.
Standardizing charts of accounts across a business greatly reduces the need for spreadsheet-centric activities. Once charts of accounts are uniform, there is no need to map from one chart to another, bypassing any reliance on spreadsheets to get the job done. Obviously, with the elimination of numerous spreadsheets, fewer material and especially human resources go into the reconciliation, consolidation, or budgeting cycles. A reduction of as few as 10 FTE represents an annual savings of roughly $1 million each year. Importantly, the end product is better. Not only is accuracy improved by the elimination of spreadsheet cell formula errors, potential data entry errors are avoided because correct and complete data is available company-wide by queries against the ERP system. Instead of the collection of desktop generated spreadsheets, the same function is accomplished by reports that can be standardized across the company and are, in essence, printed straight from the general ledger or other data present in the ERP system. Moreover, the reports can be more timely because they eliminate the delay inherent in producing the spreadsheet efforts. The end result of reports against a standardized chart of accounts is to provide the same information more quickly based on up to the moment data that is in the general ledger, rather than older data that was inserted as a value in a spreadsheet.
| < Prev | Next > |
|---|
Related Articles
- Apples to Oranges: What is Your Financial Consolidation Comparing?
- Everyone Takes the Hit: What You Can Do About It – 5 Key Business Metrics and Oracle E-Business Suite
- Globalized Financials in R12: Avoiding the Risk of Nuclear Disaster
- Basic Accounting for IT - Part I
- Getting the CFO to Pick Up His Bottom...Line: Best Practices in Cutting Costs
Enter your email address to sign up for our Newsletter
May Puzzle
David is often referred to as Rainman due to his peculiar ability to effortlessly figure out a certain date's day of the week. He recently displayed this talent when I asked him if there was a conflict with the upcoming Fuzzy Dice Conference and our weekly court-ordered community service. He asked the date of the convention. It was April 20th, 2012.
"Oh, that’s a Friday," he said, effortlessly. "And your sentences have you committed for the next few dozen Wednesdays so you'll be able to go." And of course he was right.
One day a few weeks ago I asked out loud in the office about the date June 5th. And of all people, my brother Tommy piped up and said "Oh, that's a Tuesday."
"That's right," said David.
Well how about Otcober 3rd?
"That's a Wednesday," said Tommy. Then I asked about Christmas Day 2012.
"Oh, that's a Tuesday." David nodded in agreement.
Do we now have two rainmen? Or had Tommy figured something out?
Solution
Here's what was going on. Tommy was using something called anchor dates. And these dates apply to each and every year. April 4th, or 4/4 we’ll call it from now on, June 6th or 6/6, 8/8, 10/10, 12/12, are all the same day of the week, each and every year.
So too are 5/9 and 9/5, May 9th and September 5th. So too are 7/11 and 11/7, and all the above dates are the same day of the week, as is the last day in February, Leap Year or not. And they’re all the same day as January 4th, it would otherwise be January 3rd, but this was a leap year, and that’s changes the anchor day from January 3rd to January 4th.
Tommy also knew that New Year's Day was a Sunday. He was sobered up by then. And he knew it was a Sunday because Christmas was a Sunday in 2011, so New Year's Day is a Sunday, so the Anchor Day for 2012, January 4th, has to be a Wednesday!
So if that's a Wednesday, then 4/4, 6/6, 8/8, 10/10, 12/12, 5/9, 9/5, 7/11, 11/7, and February 29th are all the same day of the week, and they're all Wednesdays. So when I ask for example, about October 3rd, he knew October 10th was a Wednesday, 10/10. So 10/3 must also be a Wednesday. 12/12 is a Wednesday in 2012, so it’s 12/26, which is two weeks later. So 12/25, or Christmas Day, must be a Tuesday.
Success Tips for Oracle Project Management
- Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
- Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
- If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
- Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
- Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
- Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
- Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
- Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
- Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
- Include governance, risk, and compliance management as part of the project plan.
- Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.
The Analyst Corner
John Van Decker, Research VP of Gartner, states:
"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."
Popular Articles
- Organization Setup in R12
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- 11i to R12 Decision: Upgrade or Reimplement?
- Designing a Global Chart of Accounts and Taking Advantage of Oracle® E-Business Suite Release 12
- Moving from GAAP to IFRS with Oracle EBS





