The Accountability Framework
Governance, reporting, audit, assurance, controls, compliance, and accounting all exist to answer the same question:
Can an actor demonstrate, with sufficient evidence, that they have fulfilled the responsibilities entrusted to them?
Governance exists to establish accountability, accounting exists to support accountability, reporting exists to communicate accountability, and audit exists to validate accountability. Accountability is the production, communication, and validation of accountable behavior. Trust is the output of accountability. Accountability is part of a virtuous cycle. A feedback loop. A causal chain. A cybernetic loop.
Big Picture
Here is accountability described in a few different ways and relative to some other things. Start with this:
- Governance creates norms.
- Accountability binds norms to actors.
- Accounting captures evidence of behavior.
- Reporting communicates claims about behavior.
- Assurance tests those claims against evidence.
- Trust enables governance decisions.
- Governance revises norms.
Another take might be:
- Governance creates Norms
- Accountability creates Obligations
- Accounting creates Evidence
- Reporting creates Claims
- Analysis creates Insights
- Assurance creates Confidence
- Trust enables Decisions
- Governance revises Norms
Or, more compactly:
Norms >> Responsibilities >> Behavior >> Evidence >> Claims >> Assurance >> Trust >> Governance
The interesting thing is that governance begins with norms and the loop returns to norms. Audit is therefore not merely verification; it is the mechanism that allows norms to evolve.
- Governance creates responsibilities
- Responsibilities require accounts
- Accounts require accounting
- Accounting produces reports
- Reports require assurance
- Assurance informs governance
I think the entire chain can be expressed as transformations of a single object:
- Governance creates norms
- Accountability creates obligations
- Accounting captures evidence
- Reporting creates claims
- Audit tests claims against evidence
- Governance acts on the result
Said another way:
Governance > Accountability > Accounting > Reporting > Audit / Assurance > Trust > Better Governance
Governance Defines What Matters
Governance is the overarching framework of rules, policies, incentives, and authority structures that defines how an organization is directed, controlled, and aligned with its stakeholder mandates. Governance answers:
- Who has authority?
- Who has responsibilities?
- What objectives are we pursuing?
- What rules must be followed?
- What outcomes are considered acceptable?
Without governance, there is nothing to account for.
Governance creates obligations, permissions, rights, and responsibilities. Governance defines the mandate, sets risk parameters, delegates authority, and institutes the rules of engagement.
See this blog post, Towards Semantics and Algebra for Governance. Specifically note this formula provided by KROG: (K ∩ R ∩ O) ⊆ G. That formula is a subsumption axiom or description logic that says something like, "Every valid action satisfies Knowledge (K) intersection with Rights (R) and intersection with Obligations (O) and which remains contained within Governance (G)." Or, "Every individual that is simultaneously a member of Knowledge, Responsibility, and Obligation is also a member of Governance."
That formula explains algebraically the conditions under which governance can exist.
Stewardship
Stewardship may sit between governance and accountability.
Stewardship asks:
- How should entrusted resources be cared for?
Accountability is Governance Made Relational
Accountability is the obligation of agents (management) to answer for their decisions, stewardship, and performance to principals (owners, regulators, society). It is the human or institutional willingness to bear the consequences of the system's output.
If governance creates responsibilities, accountability creates the relationship around those responsibilities. Accountability answers:
- Who must explain themselves to whom?
- Who owes an account?
This is an underappreciated point. The word "accountability" originates from the idea of rendering an account. Historically: Principal ← Account ← Agent
The very notion of accountability presupposes: an accountable party, an audience, an expectation, evidence.
No accountability without the possibility of giving an account. Accountability is the structural condition created by governance. Because authority is delegated, the agent (management) incurs an inescapable obligation to render an account of their stewardship back to the principal (investors).
Accountability enables the possibility of trust.
Controls
Controls may sit between accountability and accounting.
Controls provide the mechanisms ensuring actions conform to governance. Examples:
- approvals
- segregation of duties
- reconciliations
- authorizations
Accounting is the Mechanism for Producing Accounts
Accounting is the systematic measurement, classification, and recording of economic or business events in the form of financial transactions. It is the formal language/grammar used to translate chaotic physical reality into a structured, machine-interpretable information model. Accounting answers:
- How do we represent what happened?
Accounting is fundamentally about creating a faithful representation of: events, resources, obligations, rights, outcomes
Notice how close this is to governance. Governance defines obligations. Accounting records fulfillment (or non-fulfillment) of obligations.
Accounting converts reality into evidence.
Accounting assumes a measurement process. Accounting also assumes semantics. Before something can be measured or reported: What is it? Is it an asset, a liability, equity?
Accounting is the direct technical response to accountability. To "render an account," you must first build an accounting system. It translates physical transactions, obligations, and assets into an immutable, structured semantic ledger of business event information.
A business events journal is used to provide an accounting.
Reporting Communicates the Account
Reporting is the structured aggregation and communication of that ledger information to internal and external stakeholders at defined intervals. It is the dashboard or API through which the organization exposes its state. An account sitting in a ledger is not yet accountability. Someone has to communicate it. Reporting answers:
- What happened?
- How is the account presented to stakeholders?
Examples: Financial statements, Sustainability reports, Regulatory filings, KPI dashboards, Public sector reports.
Reporting transforms accounting records into claims. Claim: "We spent the funds appropriately." Supported by: Accounting records.
Reporting should be based on evidence. A Claim in a report is supported by evidence. Documentation of some Event provides the Evidence which is the basis for an Accounting which is then ultimately Reported.
Reporting is the interface layer. It synthesizes and structures the granular information stored in the accounting ledger into standardized views (financial statements, operational dashboards, disclosure filings) for internal and external consumption.
A reporting framework is used to create a report. See the Theory of the Financial Reporting Framework.
Analysis is implicitly a part of reporting. Reporting feeds analysis. Financial Planning and Analysis (FP&A) is a part of analysis.
Analysis Figures out What the Reporting Means
Analysis interprets claims and evidence to support decisions. While reporting communicates what happened; analysis figures out what it means. Analysis creates insights.
Reporting produces claims, but governance rarely acts on raw claims. It governance acts on analyzed claims. Analysis is therefore the mechanism that converts accountability information into decision-useful knowledge. Into insight.
Standard reporting frameworks enable consistency and comparability across economic entities and across periods of time by defining standard report line items and subtotals to report state and changes in state.
Audit and Assurance Test the Claims
Audit (a.k.a. assurance) is the independent, systematic examination of the ledger, reporting mechanisms, and governance compliance to establish trust, detect anomalies, verify evidence, and validate provenance. This is the verification layer. Audit answers:
- Can these claims be trusted?
It examines: evidence, controls, processes, records, assertions. Audit sits between reporting and trust. Without audit: Reported trust. With audit: Verified trust. This is why audits are often described as enhancing confidence.
Audit/Assurance sits between the reported interface and governance/accountability. It independently examines the reporting (to ensure it faithfully represents the accounting ledger) and the accounting rules/controls (to ensure they comply with governance mandates). The audit provides immediate feedback on the specific accountability of the actors, which in turn triggers systemic feedback to refine future governance.
An audit evidence graph is used to document claims. An audit is used to assess risk, evaluate controls, measure control activity, and test claims.
Trust is the Actual Product
This is the piece many frameworks omit. People often think: Accounting → Financial Statements
But societally: Accounting → Reporting → Assurance → Trust
Investors do not buy financial statements. They buy confidence in financial statements. Citizens do not want reports. They want confidence in government actions.
Trust is the real output.
At the macroeconomic or organizational level, the end product is trust. Trust is not a soft sentiment; in economic systems, it is a reduced cost of capital, lower transaction friction, and institutional legitimacy. The system takes raw, unverified operational chaos and processes it through standardized rules and independent verification until it yields a high-grade, trustworthy signal.
From an information architecture perspective, the product is traceable, audit-ready state truth. It is a decision-grade signal where every aggregated number on a high-level dashboard can be deterministically traced backward through the reporting interface, down to the granular semantic ledger, across to the operational transaction, and up to the specific governance mandate that authorized it.
Trust is the glue that holds the accountability framework together.
The Modern Failure Mode: Fragmentation
In many modern enterprises, this chain breaks down because the components are treated as disconnected silos rather than an integrated system. For instance, when accounting relies on unstructured, unconstrained electronic spreadsheets rather than standardized, machine-interpretable data schemas, downstream reporting becomes fragile. Consequently, audits devolve into expensive, retroactive sampling exercises rather than continuous, automated verification. Further, the possibility of fraud increases because every gap is an opportunity to circumvent the system. With the typical Fortune 1000 public company using typically 800 spreadsheets to create their external compliance report; that fragmentation becomes problematic.
When the underlying information model lacks semantic precision, true accountability dissolves behind a fog of ambiguous reports, rendering governance reactive rather than structural. This semantic fragmentation is likewise problematic, particularly in the age of artificial intelligence.
The Accountability Framework
The Accountability Framework is a closed governance system that connects authority, responsibility, evidence, and trust. Governance establishes the norms, objectives, rights, and obligations that guide behavior. Accountability then creates the relationship between actors and stakeholders, defining who is responsible for what and to whom an explanation is owed. In this sense, accountability is the bridge between governance and action. Further, The Accountability Framework is a holon. The Accountability Framework interacts well/nicely with digital immutable shared ledgers.
Accounting, reporting, and assurance provide the information infrastructure that makes accountability possible. Accounting captures and organizes evidence of events, decisions, and outcomes. Reporting converts that evidence into understandable claims about performance, compliance, stewardship, and value creation. Audit and assurance independently evaluate those claims against underlying evidence, increasing confidence in their reliability and credibility.
Together, these elements form a continuous feedback loop: governance creates norms; accountability assigns responsibilities; accounting records evidence; reporting communicates claims; assurance validates those claims; and the resulting trust informs future governance decisions.
The framework can therefore be understood as a cybernetic system for aligning behavior with expectations through evidence-based accountability, enabling organizations and societies to learn, adapt, and govern more effectively over time.
Note that this framework is not about workflow of information; it describes the logical structure of accountability itself. In a workflow the focus is on "what happens next?" In logic the focus is "what must be true?" In this case, "what must be logically true for accountability to actually exist?"
The framework explains the conditions under which governance exists. It does not assume governance; it explains governance. Governance is defined in terms of other concepts: Knowledge, Rights, and Obligations. It is mathematical; not a process. Governance is a universal semantic pattern.
General Accountability (e.g. not just financial accounting)
- Governance ≡ Knowledge ⊓ Responsibility ⊓ Obligation
- Accountability ≡ Responsibility ⊓ Explainability
- Accounting ≡ Observation ⊓ Measurement ⊓ Representation
- Reporting ≡ Representation ⊓ Communication
- Analysis ≡ Claims ⊓ Interpretation
- Assurance ≡ Claims ⊓ Verification
- Trust ≡ Assurance ⊓ Acceptance
- Resources = Obligations
- Accounting ≡ Creation of a faithful and trusted representation of some reality through provable evidence
- Reporting ≡ Claims communicated
- Assurance ≡ Confidence and trust produced through examination
- Accounting ≡ Observation ∩ Measurement ∩ Representation
- Accounting ≡ Evidence Creation
- Reporting ≡ Communication of Claims
- Analysis ≡ Interpretation of Claims
- Assurance ≡ Validation of Claims
- Trust ≡ Belief supported by Assurance
- Governance ≡ Knowledge ∩ Responsibility ∩ Obligation
- Trust = Accountability + Governance
- Governance = Knowledge + Responsibilities + Obligations
- Accounting = Business Events + Accounts + Provenance + Trackability/Traceability
- Report = Claims + Reporting Framework + Interface
- Assurance = Report + Evidence + Verification
- Accountability = Report + Audit + Governance
"Declarative machine interpretable artifacts are the working medium of intent."
Conversation vs Dialogue
A "conversation" and a "dialogue" are both forms of communication; but they have very distinct differences. Conversations tend to be more informal, spontaneous, unstructured. A dialogue is a particular kind of conversation which tends to be more formal, purposeful, intentional and focused, and structured. Conversation is exchanging words. Dialogue is jointly exploring meaning.
You can have a conversation without dialogue. For example, two people can exchange facts and opinions without ever trying to understand one another. But every genuine dialogue is a conversation because communication is occurring. A pragmatic knowledge management system enables dialogue.
The accountability framework enables the possibility of having an effective dialogue; human to human, human to machine, machine to human, machine to machine.
- Holonic Thinking
- Triple Entry Accounting and Shared Ledgers
- Semantics of Accountability
- Towards Semantics and an Algebra of Governance
- Accounting & Audit by Design (A&AD) Framework
- Essence of Accounting
- Connecting Industrial Engineering, Informatics, Pragmatic Knowledge Management Systems
- From Janitor to Curator: Refactoring Accounting for the Age of Artificial Intelligence
- Examining the Importance of Accountability as a Virtue
- The Accountability Cycle
- An Accountability Framework
- Multisectoral Accountability Framework (WHO)
- Trust Physics (ebook)
- Engines, Reasoners, Theorem Provers
- COSO Framework Explained for GRC
- Internal Control - Integrated Framework (COSO)
- COSO Framework Explained in 12 Minutes | 5 Components + RCM Template
- Trust Issues
- MIT Says 95% Of Enterprise AI Fails — Here’s What The 5% Are Doing Right
- International AI experts warn of potentially catastrophic risks from AI

Comments
Post a Comment