.

Thursday, February 23, 2012

Activity Based Costing


Activity-Based View of Cost 

The groundswell of ABC occurred in the mid-1980s. This approach was born to emphasize what is being done and what it costs to do it. Activity-Based Costing provided for a real understanding of the activities being performed by each department. While a direct cost method may assign costs to the correct objects, without the ABC view, it is still difficult to understand how to reduce costs or what the resources are actually doing. 

The view of ABC originated in the resource center (albeit the resource view was most likely embedded within the general ledger [G/L] account coding), but the focus was to “convert” the G/L account view of the resources to a process per-spective. Exhibit 1.2 illustrates a traditional ABC cost flow. In this example, the G/L account view within the  Distribution Support resource/cost center is con-verted into the view of the processes supported by that center, for example, Enter Documents and Schedule Laborers processes

The normal conversion routine was to establish a “resource driver” via an interview process, thereby gaining a snapshot perspective of the effort expended on each activity. The most common process breakdown was formulated by inter-viewing the resources or the cost center manager to determine a percentage of time spent on each process. This weighting factor became the resource driver or apportionment tool for costs assigned to the process view. 
Achieving the activity view in this manner did provide an activity perspec-tive on costs. However, the perspective was achieved based on a primary as-sumption that, in order to reduce model maintenance workloads, the relationships would be frozen in a given point in time, for example, annually, semi annually, or quarterly at best. Also, in addition to the risks posed by using a stagnant model, the new activity view sacrificed and minimized the perspective of the resource view. The limited expression of resources along with the technical limitations of the computer hardware used to accommodate the models led to a number of weaknesses in the ABC models and in the information these models provided. 

Weaknesses in the ABC models were:
• Models were backward-looking, using only historical data. The models had no predictive perspective at all.

• Causal relationships, particularly those between resources and processes, were expressed only in value or in ratios/portions of value.

• Models were usually of a step-down nature, that is, costs flowed from re-sources, to activities, to final cost objects. Fully burdened resource costs were not provided.

• Models were very maintenance intensive. 

• Models had limited ability to deal with complexity.

• Because they were stand-alone models, there was the need to “feed the beast” with all the information required to run the model.

Weaknesses in the information provided by ABC were:
• All costs for a period would be spread to products without regard for actual utilization levels. This full absorption approach spread costs to products indiscriminately. Companies that utilized ABC information potentially faced the fixed cost death spiral.

• Because the nature of cost was viewed inconsistently, the ability to provide accurate gross and contribution margin was limited.

• From a control perspective, the capabilities were limited in that plans were static, and the ability to generate authorized reports generally was not supported.

• Limited variance calculations was available.

• The weak resource expression led to ineffective capacity management capabilities.

• Activity-Based Budgeting (ABB) efforts have a tendency to overstate the budget because all costs are usually extrapolated, including fixed costs.

Traditional costing certainly no longer supports management accounting needs. ABC provides more analytical capabilities, yet, as can be seen from the weaknesses listed, it does not completely support the needs of management ac-counting. Therefore, there is an identified gap in the tools and abilities to fully support management accounting.

Thursday, February 9, 2012

History of SAP

SAP's story is one of a steady rise from a small, five-man operation headquartered in southwest Germany's Rhine-Neckar region to one of the world's largest independent software providers and an employer of more than 54,000 people in over 50 countries.


1972 - 1981: The First 10 Years

"The First 10 Years" chronicles the highlights of the company's beginnings and subsequent development – from SAP's foundation, its first software modules, and the SAP R/2 system to the company's first-year revenues, first customers outside of Germany, and first tradeshow appearance.

1982 - 1991: The SAP R/3 Era

Using four servers with 64MB of memory. Employing 100 employees and signing its 1,000th customer. Reaching the DM100 million in revenues, and expanding abroad. The development of the SAP R/3 product generation. These and other landmark events are the subject of "The SAP R/3 Era."

1992 - 2001: The Age of E-Business

Reaching €6 billion, and employing more than 24,000 employees. Trade shows and conferences. Going public, and developing new technologies and platforms. Learn more about SAP's meteoric rise in "The Age of E-Business."

2002 to Today: SAP Today

SAP's story continues with the SAP NetWeaver platform, where technologies intertwine system landscapes and information flows, integrate companies and their employee teams, and establish connections among markets across virtually any perceived barrier. "SAP Today" describes the most recent technological and entrepreneurial milestones in SAP's continuing development.

[From www.sap.com]



History of QuickBooks


History of QuickBooks

by Denise Loter

QuickBooks, one of three flagship products offered by California-based Intuit, was originally patterned after personal accounting package Quicken. Intuit executives wanted to provide a package that would offer small business owners the flexibility of an easy-to-use software package and the structure and compliance required to run a profitable business.
At its launch in 1998, QuickBooks was very popular with business owners with no formal accounting background. Unfortunately, although the package was easy to use and offered significant benefit to its customers, many accounting professionals felt that it lack the security, audit trail and robustness really needed. These concerns were exacerbated because many business owners used QuickBooks, which quickly established an 80% market share, for day-to-day bookkeeping – but relied on professional accountants for month-end and year-end services.
Intuit sought to bridge this gap, and by 2000 the software included several of the missing features including audit trails, double entries and other accounting-industry compliant items. Next, Intuit began developing niche products: including those with basic or advanced features, as well as packages tailored to the needs of specific industries like contracting, retail, manufacturing and even not-for-profit. QuickBooks also leveraged the relationship between small business owners and accountants/bookkeepers by developing the Pro Series, which is specifically designed for accounting professionals who support multiple small business clients.
More recently, enhancements to the QuickBooks line have included payroll processing, remote access options, electronic payment functions, online banking, import and export options from Microsoft Excel. QuickBooks Enterprise Solutions, a product aimed at larger organizations that run accounting via  networks was developed and now runs in both Windows and Linux server environments.
Today QuickBooks continues to hold a dominant share of the market. Far from an adversarial relationship with accounting professionals, Intuit now has a network over 50,000 CPAs, bookkeepers, and consultants who serve as QuickBooks ProAdvisors. These professionals offer an array of services including QuickBooks training, technical support, consulting services, full-charge bookkeeping all targeted at the QuickBooks platform.