What it means
Accountability is easy to confuse with responsibility, but the two are different. Responsibility is about who does the work; accountability is about who has to explain and answer for the result, and who cannot pass the question on to someone else.
A team can share responsibility for a project, but usually one named person is accountable for it. The machinery of corporate accountability is mostly unglamorous.
Audited financial statements, board audit and remuneration committees, delegated authority limits, internal audit, whistleblowing channels and written minutes all exist so that decisions leave a trail that someone can inspect later. When a company is criticised for poor accountability, the criticism is often that this trail is missing or that nobody in particular owned the decision.
It matters commercially because it affects the price of money and the willingness of others to deal with you. Lenders and investors discount businesses where they cannot see how decisions get made, and large customers increasingly ask suppliers to evidence their governance before signing.
Weak accountability also raises the cost of failure, since problems surface late and remediation is more expensive. Applying it inside a business is largely a matter of design.
Sensible organisations write down who can approve what up to which value, keep a register of the decisions that must go to the board, and make sure every significant risk has a named owner rather than a committee. Reviewing those documents once a year, and after any incident, keeps them honest.
The important nuance is that accountability is not the same as blame. A healthy system asks what information was available, whether the process was followed and what should change, rather than looking for someone to punish.
Systems built purely on punishment tend to produce careful paperwork and slow, hidden problems. Accountability also sits alongside, but is not identical to, corporate social responsibility.
Social responsibility is about what a company chooses to do for its wider community; accountability is about being answerable for whatever it does, including the commitments it makes voluntarily.
In practice
Real-world examples.
Example
A mid-sized logistics group discovers that a depot has been under-reporting vehicle defects for a year. The board traces the reporting line and finds that no single manager was accountable for fleet safety data, so it appoints a named director, adds a monthly safety report to the board pack and requires the internal audit team to test the numbers twice a year.
Example
A software company signs an enterprise customer whose procurement team demands evidence of decision-making controls. The finance director produces the delegated authority matrix, the last two internal audit reports and the minutes of the risk committee, and the contract clears review in a fortnight instead of the usual three months.
Example
A charity retailer overspends on a shop refit by 60%. Because approval limits and change orders were documented, the trustees can see exactly where the extra cost was authorised, hold the right person to account and tighten the limit for future projects rather than debating who said what.
Case study
Seen in the real world.
The following is an illustrative and fictional example. Melrose Kitchenware, an invented mid-market manufacturer, grew from 90 to 600 staff in four years and kept the informal habits of a small firm. Purchase orders were approved verbally, three managers all believed someone else was watching supplier quality, and the board saw only a summary profit figure each quarter.
When a batch of faulty handles led to a product recall, the review found no record of who had approved the change of supplier or on what evidence. The cost was not only the recall itself but the six weeks the leadership team spent reconstructing the decision.
The response was deliberately dull: a written approvals matrix, a single named owner for supplier quality, a standing risk report to the board and a rule that any supplier change above a set value needed documented sign-off. Two years later the same team handled a similar quality alert in four days, because the paper trail told them immediately who had decided what.
Watch out
Common mistakes.
- Treating accountability as a compliance exercise for the audit file rather than as a practical question of who answers for a decision.
- Making a committee accountable, which in practice means nobody is, because a committee cannot be asked to explain itself in the way a person can.
- Confusing accountability with blame, which drives people to hide problems and produces exactly the surprises that good governance is meant to prevent.
Questions
People also ask.
Who is ultimately accountable in a company?
The board of directors, which can delegate responsibility for work but not its own duty to answer for the results.
Does accountability slow a business down?
Well-designed accountability speeds decisions up, because people know the limits of their own authority and stop escalating routine matters.
How do you evidence accountability to an outsider?
Through documents that show the decision path: authority limits, minutes, risk registers with named owners, and audit reports that test whether the stated process was actually followed.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%