The terms research and development are often used imprecisely. Each may have a myriad of connotations, and even though these two words often are used together, each represents a different process with differing implications in terms of planning and control. Research as used herein relates to those activities in a business enterprise that are directed to a search for new facts, or new applications of accepted facts, or possibly new interpretations of available information, primarily as related to the physical sciences. It is the activities or functions undertaken, often in the laboratory, to discover new products or processes. Development, however, as discussed herein, denotes those activities that attempt to place on a commercial basis that knowledge gained from research. In another sense, the efforts discussed in this chapter are those that normally would be managed by the vice president or director of research and development (R&D).
Although R&D activities may be grouped in any number of ways—and proper classification is important in the planning and control function—this segregation is often used internally by those entities that do extensive work in these three areas:
For those financial executives who deal with budgeting efforts in the R&D area, and who are desirous of having the activity defined, here are separate definitions for “research” and “development.”
The most effective assistance of the financial discipline in respect to the planning and control of R&D expenses probably must recognize the role these expenditures can and should play in the economy as well as in a given business.
R&D in the United States is conducted by a diverse number of institutions: the federal government and other governments; industry; universities and colleges; nonprofit types of organizations; and professional firms that conduct research for others. Although the efforts of these groups have resulted in the technological superiority of the United States in the mid-twentieth century, now it has become evident that reduced expenditures at the federal level and a hostile climate for new ideas and products are threatening this position. Whether it be because of uncertain business conditions, shortsighted corporate management, lack of adequate incentive, unacceptable governmental regulation or procedures, the fact remains that such a trend may well have adverse implications for the U.S. economy.
There is evidence, in an aggregate sense, of the relationship between technical innovation and the stimulation of economic development. Within a given manufacturing company, in terms of a particular project or projects, perhaps no simple cause-and-effect relationship between R&D expenditures and net income can be found. However, statistical correlation suggests a tendency for earnings to increase, over a period of time, with an increase in research spending. Empirical data tend to show that under the private enterprise system, industrial firms grow and prosper by developing, or investing in new products or processes, or improving existing ones. It simply is not enough to do reasonably well that which is being done, for competitors will pass by such a business. Innovation or improvement and management of change are the intangible attributes that distinguish the progressive company from one on the road to decline. And the wise planning and control of research and development costs should recognize this relationship.
In a very real sense, the funds spent on R&D are quite different from many other expenses. They are an investment in the regeneration, growth, and continued existence of the business and should be evaluated, insofar as possible, as an investment.
From the strategic and long-range viewpoint, the important corporate activities should support the corporate goals and objectives. Certainly research and development efforts should fit this category. For example, if an entity is planning substantial growth in the compact disc field, then research and development in this area should be considered. Conversely, if strategic plans call for divestiture of a television operation, then it makes little sense to expend sizable sums on R&D in this field. Moreover, R&D input regarding acquisition targets, competitive R&D activity, or the state of the art should be helpful in strategic planning. Further, strategic planning should consider the alternative of performing research in-house or of purchasing an entity already active in the product line.
This preferred relationship between corporate objectives and the R&D plan is shown in Exhibit 6.1.
Aside from understanding the proper relationship of R&D to corporate objectives, the increased competition, the often critical time factor in developing new products, and perhaps greater wisdom about the nature of R&D, is forcing a new approach in many complex R&D situations. This viewpoint has been denoted as system focus by one author.1
System focus is a philosophy which emphasizes the importance of technology integration early in the process: the mutual adaptation of new technology, product design, the manufacturing process, and user needs.
The traditional approach to R&D might be regarded as one group of executives after another adding its contribution to the developing product and then passing the task later to others down the line—in the engineering department and then in the manufacturing process and finally in marketing. This transfer of knowledge is mostly downstream. Often there is little incentive or no mechanism for sending knowledge back upstream so it can improve the technology in the next go-around. In the systems-focused organization, the goal of new product development shifts from a compartmentalized sequential approach to optimizing the whole system. Under such circumstances, the company early in the R&D process forms an integration team composed of a core group of managers, scientists, and engineers. This team investigates the impact of various technical choices on the design of the product and the manufacturing system.
The purpose of this brief section is to alert the controller to the time and cost savings inherent in this systems integration. The controller should be aware of the potential in any relevant discussions with the R&D manager, and in the formulation of the planning and control system.
Another relevant background matter is organization. The importance of the R&D function in many companies has led to the establishment of separate organizational units, such as a division or subsidiary. Although the size of the company, scope of the research function, management philosophy, and type of research may influence the organization structure, a pattern is discernible in a review of different corporations. A self-contained unit is illustrated in Exhibit 6.2. The financial officer handling the financial aspects of R&D activity reports to the vice president of Research and Development, and provides the necessary financial analysis, accounting and reporting services, and coordination with the corporate finance group. In this instance, a “dotted line” relationship is maintained with the corporate vice president and controller.
The precise manner in which the R&D function is organized directly affects the accounting for the activity. The organization responsibilities, as defined by the functional outline or charter, provide the basis for budgeting and controlling the costs. The reporting and measurement of expenses must be guided by the organization plan; it must parallel the responsibilities of each organizational unit.
In public corporations, prior to the mid-1970s, there existed a wide difference in the balance sheet treatment of R&D costs. Given the tendency or desire in some quarters to report the highest possible earnings, as well as the high degree of uncertainty about the future economic benefits of individual R&D projects, such variations are understandable. Therefore, because of this reason, among others, and before deciding on the preferred accounting treatment of R&D costs, the Financial Accounting Standards Board (FASB) in 1973 considered four alternative methods of accounting for such costs as incurred:
The FASB concluded that all R&D costs (except those covered by contract) should be charged to expense when incurred. This treatment was to be effective for fiscal years beginning on or after January 1, 1975.
The above comments relate to R&D costs exclusive of costs of developing of software. U.S. firms may account for the costs of development of similar software products in different ways. Some costs of development of software to be sold, leased, or otherwise marketed, may be capitalized. All the costs of development of similar software created for internal use may be expensed by some firms and capitalized by others.
There seem to be differences of opinion between the Institute of Management Accounting (IMA) and the FASB. The results of a survey by Kirsch and Sakthivel published in January 1993, covering 139 completed questionnaires mailed to 417 of the Fortune 500 companies showed this treatment of software development costs:
Readers, if interested, can keep updated on the directives concerning accounting for software development costs.
The Statement of Financial Accounting Standards No. 2 does not apply to the costs of R&D conducted for others under a contractual arrangement; this is covered by statements relating to accounting for contracts in general. It does apply to the types of costs discussed in this chapter but not incurred under a contract to outside parties.
Elements of costs identified with R&D activities would include costs of (a) materials, equipment, and special facilities, (b) personnel, (c) intangibles purchased from others, (d) contract services, and (e) indirect costs. Illustrative activities, the costs of which typically would be included in R&D and would be expensed unless conducted for others under a contractual arrangement as outlined in the FASB's Statement No. 2, include:
If an activity fits into one of the above categories, then a controller should categorize any related expenses into a format that clearly breaks down expenditures for each R&D activity. Before going into the details of this breakdown, however, it is reasonable for a controller to determine the size of expected R&D expenditures. If they are comparatively small, it may be easier to roll the R&D costs into overall engineering expenses and not go to the expense of creating a separate categorization. However, if the costs are significant, costs should be grouped into the following five categories for reporting purposes, or some similar format:
Though it is important to group expenses into the proper R&D categories, it is equally important to exclude some expenses, primarily those that are no longer strictly concerned with R&D activities, but rather with commercial production. These excludable expenses are:
Now that much of the background information has been briefly reviewed, it might be useful to discuss some of the areas where the knowledge of the financial executive should be helpful to the research director before talking about the technical financial aspects relating to planning and control of R&D costs.
Primary responsibility for the R&D activities rests with the officer in charge of the function. However, the corporate controller and the cognizant financial executive assigned to the R&D financial duties should be knowledgeable and exercise leadership in these areas (not necessarily in the order of importance):
The remainder of this chapter relates to specific questions or tasks in the planning and control of R&D expenses.
By and large the planning and control of R&D expenses in the United States are handled through a budgetary process. The seven principal steps are:
“How much should the company spend on R&D this year?” A great many managers ask this question. And since expenditures should give weight to the long term, the query is really a multiyear one. There are innumerable projects which innovative R&D executives can conjure up; but there are limits on what a company should spend. Many constraints must be considered, including these, in determining the total R&D budget for any given time period:
So, if the constraints are known, there are several guidelines in current use for determining the limits of R&D spending. Some of these measures are useful guides in determining the overall budget:
Aside from internal experience data developed from company records by either the R&D director or the controller, some useful information may be obtained from several external sources. Thus, trade associations may have available data on a particular industry. The Industrial Research Institute, Inc., of Washington, DC, may be another source. If a company is required to file a Form 10-K with the Securities and Exchange Commission (SEC), this document may be available. Further, most of the national business publications such as Business Week, Fortune, or Planning Review and others periodically discuss the subject. One of the best sources is the annual “R&D Scoreboard” published in June or July of each year by Business Week. Typical material in each annual report is similar to this:
For example, in 2005 it was reported that R&D managers were learning to “make do” in a period of difficult economic times by such actions as:
Of course, any R&D statistical information must be carefully interpreted in that the start of major new projects or the cessation of completed ones can severely impact the quantified results of a company's effort.
Determining the total amount to be spent on R&D for the planning year merely establishes a maximum limit on aggregate expenditures. In terms of effective planning and control, three related segments of the total operating expenses need to be determined:
Because many departmental expenses depend on which projects will be undertaken and on the estimated cost of each, the project selection and cost estimating are discussed first.
The selection of the particular R&D projects is primarily the responsibility of the research director, giving weight to resources available, the amount of risk found acceptable by management, the strategic plan of the company, and a proper balance between the various types of projects.
In a practical way, a judgment will be made about the relative amount of effort to be spent on various categories of projects. A typical categorization might include these, perhaps in the order of ascending risk or cost, or reducing chance of economic return:
Numerous influences will enter into the decision of project selection. The research director, for example, probably would consider these factors, among others:
The projects to be initiated will depend on the judgment of the research director and other members of top management. However, these general observations are made, including some comments as to how a controller or financial executive may be useful:
It is no easy task to decide on an economic basis whether R&D on a given project should be undertaken. However, there will be instances when it can be attempted.
Consider, first, return on assets (ROA), sometimes described as return on investment. The cost–volume–profit relationship may add a dimension to the R&D investment decision.
Assume these five conditions:
With this sales and gross margin expectation and a minimum 10% return on assets, how much can the company spend on research and development on Product T?
Some indication of the approximate expenditure level can be gained from this calculation:
Simplify:
Proof:
The $27,333,333 permissible R&D can be converted to a budgeted amount per annum.
Another quantitative analysis related to percent return on net sales. Some managements judge the acceptability of a product by the adequacy of its percent return on sales.
Make these three assumptions and then decide how much can be spent on R&D for the product:
The calculation is:
wherein again,
Simplify:
Proof:
As previously mentioned, one factor in determining how much should be spent on a given project is the risk of that project. Although it may be difficult to calculate risk, analysis (by the controller) may provide management with some sense of the relative risk. One approach is based on the logical assumptions that (a) risk increases as a company ventures into new markets and new products, and (b) risks also increase with time from the completion of R&D until product sales commence. The concept is illustrated by the matrix in Exhibit 6.4 wherein the market objective and the time span are the factors of risk. The objective of a completed matrix is to graphically illustrate how relative risk for the planning year compares with the prior year, or how risks on R&D in one division compare with another or how one project may relate to another.
The four steps in identifying the relative risk are:
As illustrated in Exhibit 6.6, 30% of the expenditures in planning year 1 (20XX) are contemplated in the area of most risk—new products in new markets, as compared with only 5% in the market area deemed least risky.
The research director must judge how prudent such risk is, together with the return on assets for completing products, the total potential return, and so on.
Having reviewed how the overall expenditures for R&D for a given year might be determined, some of the influences in determining what projects might be considered, and a couple of illustrations of a possible quantitative approach to judging the desirability of a given project, it might help to summarize a typical budgeting procedure and provide budgetary examples.
These are the eight steps that the research director might take, with the assistance of the controller or financial executive, in some phases:
As previously explained, the control phase of the budgeting process consists of comparing actual expenses and budgeted expenses for the indirect or administrative type expenses of the R&D function. Project direct expenses also could be judged in the same fashion. But it makes more sense, in this latter case, to compare estimated total expenses to complete the project—a continuous or monthly updating process—with the project budget. In this manner, if it appears that expenses are going over budget, perhaps steps can be taken to reduce some of the anticipated costs. Budgetary control probably is the most widely used method of monitoring expense trends, and correcting over-budget conditions.
In some instances, performance standards also may be used to control costs—or to supplement budgetary control. While many phases of the R&D effort are varied and not easily subject to measurement, there are circumstances where performance standards may be useful in evaluating some of the quantitative phases of the work. Some suggested performance standards for those functions that are repetitive and perhaps voluminous include:
Management has often asked, and still asks, “Are the R&D expenditures worthwhile?” or “Is the company research effective?” Questions such as these do not relate to budgetary performance or performance standard results. Rather, they go to the heart of the contribution that the R&D activity, or segments of it, makes to the economic well being of the company.
Some research efforts, such as basic research, are difficult to measure because no specific or direct objective is discernible. But the reason for some projects is clearly economic, such as the discovery of a cheaper manufacturing process or a new product. For these, a kind of measurement is possible.
Some economic measures or indices that the accountant might suggest, or perhaps assist in developing, include:
The effectiveness of R&D effort is principally the responsibility of the executive in charge of such activity. With the high level of foreign competition, in those instances where research and development is a critical success factor for the business, the process of benchmarking may be a means of increasing R&D productivity. Although this method has been used extensively with regard to manufacturing and marketing functions, it can be applied also to R&D activity. As discussed in Chapter 1, benchmarking is the measuring of a company's functions against those of companies considered to be the best in their class, and the initiation of actions to improve the activity under review.
In the event the controller is asked for advice regarding the application of benchmarking in R&D activities, the controller should be aware that the process has been a factor in creating (for the R&D function) the following benefits in some companies:
Finally, in judging the effectiveness of product development, a broad business viewpoint must be considered—not merely the R&D project and/or revenue calculated for budget purposes. Management must allow for the right combination or trade-offs between cost, time, and performance requirements. This is where the financial executive, and especially the controller, can be of assistance to other management in the periodic evaluation of product development projects. Increasingly, the controller is a member of the “stage gate” group that monitors the progress of the project.
The “stage-gate” system segregates a company's new-product process into a series of development stages. These stages are partitioned by a series of “gates” which are periodic check points for such matters as cost escalation, market changes, quality control, and other risks. Each project must meet certain criteria before it can pass through the gate and down the development path. The senior managers involved, as well as the financial executive, review progress as the product approaches its market launch. Typically, in the early development phase, accurate information is lacking and financial risk is low. As the project reaches a critical point, a detailed financial analysis is desirable. The controller's department, or chief financial officer (CFO) integrates financial analysis, technical analysis, and manufacturing and marketing plans. Revealed are sales forecasts, prices, profit margins, and possibly impact of a discontinued project. The end result is said to be more efficient development operation, more new product successes, and a more flexible cost latitude (e.g., recognizing the time factor in the product success).
The stage-gate system offers a strong role for finance, but also provides sometimes beneficial cost-time trade-offs and plan changes for the product developers.
1. Marco Iansiti, “Real-World R&D: Jumping the Product Generation Gap,” Harvard Business Review, May/June 1993, pp. 138–147.