Understanding the Concept of Responsibility Accounting in Business

Every large organisation eventually faces the same problem: costs pile up faster than anyone can explain them. A factory manager blames the purchase department for expensive raw material. The purchase department blames the sales team for unpredictable order volumes. Nobody quite owns the number. Responsibility accounting exists to fix exactly this mess by tying every cost and revenue figure to the manager who actually controls it.

What is responsibility accounting? 🔗

Responsibility accounting is a management accounting system that collects and reports financial data based on who is responsible for it, not just where it appears on a ledger. Instead of looking at the organisation as one giant pool of expenses, it divides the business into smaller units, each headed by a manager who is accountable for that unit’s financial performance. A responsibility accounting system evaluates each manager specifically on the revenue and expense items they have the authority to influence, which keeps performance reviews grounded in reality rather than guesswork.

The logic is straightforward. If a plant manager has no say over raw material prices fixed by head office, it makes little sense to judge them on material cost variances. But if they control labour scheduling and machine utilisation on their own floor, those numbers should absolutely land on their report card.

The Sorgdrager framework: Where the concept comes from 🔗

The theoretical foundation for this system is credited to Professor A.J.E. Sorgdrager, whose work is often cited in Indian commerce curricula under the title “Particularisation of Indirect Costs”. The phrase sounds technical, but the idea is fairly intuitive.

Most direct costs, like raw material used in a specific product, are easy to trace to a department. Indirect costs, like electricity, factory rent, or the salary of a shared administrative staff member, are harder to pin down. Sorgdrager’s contribution was to push for breaking these indirect costs into smaller, traceable pieces and assigning them, wherever reasonably possible, to the specific responsibility centre that actually caused them. Instead of dumping the entire electricity bill into one company-wide overhead figure, particularisation asks: which department used how much power, and can that be measured or estimated fairly?

This particularisation is what gives responsibility accounting its bite. Without it, managers could always argue that poor results were caused by costs “somewhere else in the system.” With it, the system tries to draw a clearer line between a manager’s decisions and the numbers on their desk.

The core building blocks of the system 🔗

Controllability: The central rule 🔗

The entire framework rests on one guiding rule: a manager should be judged only on what they can control. This is formally known as the controllability principle, and it separates responsibility accounting from ordinary cost accounting, which simply records where money was spent without asking who was actually in charge of that spending decision.

In practice, this means every accounting report has to clearly separate controllable items from uncontrollable ones. A regional sales manager can control travel expenses and discount decisions, but not the corporate tax rate or head-office overhead allocated to their region. Mixing the two in a single performance number would be unfair and, worse, would give the manager no useful signal about what to fix.

Alignment with organisational structure 🔗

Responsibility accounting only works if the reporting structure mirrors the actual chain of command. Each responsibility centre needs a clearly identified manager, a defined scope of authority, and a reporting line to the level above. If the accounting boundaries don’t match the real organisational boundaries, the whole exercise collapses into confusion about who owns what.

Budgets and standards as the yardstick 🔗

Every responsibility centre needs a target to compare itself against, usually a budget or a cost standard. The system requires both budgeted and actual figures for each centre, since performance evaluation only makes sense when there’s a plan to measure against. The gap between planned and actual results, the variance, becomes the starting point for every performance conversation.

Types of responsibility centres 🔗

Not every department has the same scope of control, so responsibility accounting classifies units into different types of centres depending on what the manager is accountable for.

Some organisations also use a fifth category, the discretionary cost centre, for units like HR or accounts where there is no direct, measurable link between spending and output. These centres are evaluated mainly on whether they stayed within their approved budget, since it is difficult to tie their output directly to a measurable financial result.

How it works in practice 🔗

Setting up a responsibility accounting system usually follows a logical sequence.

Step 1: Identify responsibility centres 🔗

The organisation is mapped into segments, each with a clear manager and a defined scope of authority.

Step 2: Set budgets and standards 🔗

Each centre gets a financial plan, be it a cost budget, a sales target, or a return-on-investment goal, that reflects what the manager can realistically influence.

Step 3: Track actual performance 🔗

Actual costs and revenues are recorded and, where indirect costs are involved, particularised down to the relevant centre rather than left as one unallocated lump.

Step 4: Compare and report variances 🔗

Actual results are measured against the plan, and the difference is reported back to the manager and their superior, separating controllable variances from those caused by factors outside the manager’s authority.

Step 5: Take corrective action 🔗

Significant variances trigger a review. Was the target unrealistic, or did execution fall short? This feedback loop is what makes the system a control tool, not just a reporting exercise.

Why businesses rely on it 🔗

The appeal of responsibility accounting goes beyond neat paperwork. Because responsibility is assigned according to the knowledge and skills of specific individuals, the system builds a genuine sense of ownership across departments, rather than treating cost control as something that happens only at the top.

It also supports decentralisation. When senior management trusts unit heads with clearly defined authority and matching accountability, they can step back from day-to-day decisions and focus on long-term strategy. It sharpens performance evaluation, since managers are compared against realistic, controllable benchmarks instead of company-wide averages. And because managers know their numbers will be scrutinised individually, the system naturally nudges people toward more disciplined spending.

The limitations worth knowing 🔗

The system isn’t without friction. Joint and common costs, expenses shared across multiple departments, are inherently hard to split fairly. Any allocation method chosen is, to some extent, an approximation rather than an exact science. Because responsibility centres are typically evaluated in a top-down manner, the approach can also overlook the interdependencies between departments, discouraging the kind of teamwork that cuts across organisational boundaries.

There’s also a behavioural risk. When managers know they will be judged strictly on numbers, some resort to padding budgets or delaying necessary spending just to protect their variance report. A well-designed system anticipates this and pairs financial metrics with qualitative checks, not just spreadsheets.

Bringing it together 🔗

Responsibility accounting turns a company’s org chart into a financial control map. By particularising indirect costs, as Sorgdrager originally proposed, and holding each manager accountable only for what they can control, businesses get a system that is fair to individuals and useful for the organisation as a whole. It’s less about assigning blame and more about creating clarity: who decided what, and what did that decision cost or earn.

What do you think? If a manager has only partial control over a cost, say, they can influence quantity but not price, how should a fair responsibility accounting system treat that cost? And in a highly interconnected department like shared IT services, is particularisation of indirect costs always practical, or does it sometimes create more arguments than it resolves?

References

1. https://courses.lumenlearning.com/suny-managacct/chapter/responsibility-accounting-in-management/
2. https://egyankosh.ac.in/bitstream/123456789/84045/3/Unit-17.pdf
3. https://fiveable.me/managerial-accounting/unit-9/3-describe-types-responsibility-centers/study-guide/MUdjU4pdbhCQImHw
4. https://www.wallstreetmojo.com/responsibility-accounting/
5. https://biz.libretexts.org/Bookshelves/Accounting/Managerial_Accounting_(OpenStax)/09:_Responsibility_Accounting_and_Decentralization/9.04:_Describe_the_Types_of_Responsibility_Centers
6. https://www.geeksforgeeks.org/accountancy/responsibility-accounting-types-features-objectives-examples-advantages/
7. https://maaw.info/ResponsibilityAccountingConcept.htm