Going Green in ERP

PDFPrintE-mail

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.

Add comment


Security code
Refresh

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

January Puzzle

A traveler gets lost on a deserted island and finds himself surrounded by a group of n cannibals.

Each cannibal wants to eat the traveler but, as each knows, there is a risk. A cannibal that attacks and eats the traveler would become tired and defenseless. After he eats, he would become an easy target for another cannibal (who would also become tired and defenseless after eating).

The cannibals are all hungry, but they cannot trust each other to cooperate. The cannibals happen to be well versed in game theory, so they will think before making a move.

Does the nearest cannibal, or any cannibal in the group, devour the lost traveler?

Show solution...

Solution

The short answer is the traveler’s fate depends on the parity of the group. If there is an odd number of canibals, the traveler will be eaten, but if there is an even number, the traveler will survive.

To prove this, we will consider small groups and use mathematical induction to explain the solution for larger groups.

Case n = 1: this is an obvious case. If there is one cannibal, the traveler will be eaten. It doesn’t matter that the cannibal will get tired because there are no other cannibals around as a threat.

Case n = 2: this is a more interesting case. Each cannibal wishes to each the traveler, but each knows he cannot. If either cannibal eats the traveler, then he will become defenseless and the other one will eat him. So each cannibal uses backwards induction to realize that the only strategy is to not eat the traveler. The hapless traveler finds a bit of luck, therefore, and actually survives.

Case n = 3: this is where the problem gets interesting. The best strategy is for the closest cannibal to make a move and eat the traveler. The cannibal will be defenseless after eating, but ultimately he will be safe. Why is that? The reasoning is due to induction: once the cannibal eats the traveler, the resulting situation has 2 unfed cannibals and the 1 defenseless cannibal. But as we just showed above, when there are 2 unfed cannibals, neither will make a move for fear of being eaten by the other! Thus the first cannibal to make a move will be safe as the remaining 2 cannibals block each other.

We can prove the higher cases using mathematical induction. If the number n is odd, then the closest cannibal can safely eat the traveler because the remaining number of unfed cannibals is even (and by induction, with an even number of unfed cannibals no one makes a move). If the number n is even, then no cannibal will eat the traveler, for if he did, the remaining number of cannibals would be odd, meaning he will get eaten by the induction hypothesis.

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."