Accounting Conventions and Principles with Examples

Accounting principles and conventions are words often used to explain the ideas behind recording and presenting financial information. Textbooks may group concepts differently, and a simple classroom rule is not a substitute for an applicable accounting standard. For an Indian entity, the relevant notified Accounting Standards or Indian Accounting Standards, laws and entity facts determine treatment. This guide explains common ideas—such as accrual, consistency, prudence, materiality and going concern—in plain language, then shows why each needs context. The examples are fictional and are not accounting policy or advice.

Principles, concepts, conventions and standards

A conceptual framework describes foundational objectives and concepts used to develop and understand standards. A standard sets requirements for a topic, while an accounting policy explains choices or procedures an entity applies where permitted. The words principle and convention may be used informally in education to describe recurring ideas or customary practices. They should not imply that a broad slogan overrides a specific standard. When two sources appear to conflict, identify the transaction, reporting framework, period and authoritative requirement before applying a rule. A learner should cite the current official text rather than memorizing an undated list.

Accrual and matching: connect activity to the period

Under accrual accounting, transactions and events are generally recognized when the relevant criteria are met rather than only when cash moves. A service received in March but paid in April may require a liability and expense in the appropriate period, depending on the facts and applicable requirements. The related idea often called matching encourages costs to be presented in relation to the income or activity they support, where the framework permits. It is not permission to defer any expense until revenue appears. Recognition, measurement and presentation are controlled by the relevant standards.

Going concern and consistency

Going concern is an assumption used in preparing many financial statements unless management intends to liquidate or cease trading, or has no realistic alternative under the applicable framework. It affects measurement and disclosure; it is not a guarantee that an entity will survive. A fictional business with a sudden financing problem would need a documented assessment and appropriate review rather than a casual declaration. Consistency means applying an accounting policy consistently to similar transactions when required, while permitting changes when justified and allowed, with proper explanation and disclosure where applicable. Consistency is not a reason to preserve an incorrect policy.

Prudence, materiality and faithful information

Prudence is often taught as caution when making judgments under uncertainty. It should not become deliberate understatement of assets or income, nor overstatement of liabilities or expenses. Materiality concerns whether information could reasonably influence users' decisions; it is assessed in context and can depend on size or nature. A small item can be material because of its nature, while a large recurring balance can require special attention. The IFRS Conceptual Framework highlights relevance and faithful representation as fundamental qualitative characteristics, supported by comparability, verifiability, timeliness and understandability. Local requirements and the applicable reporting framework still govern.

• Accrual: consider when the underlying event and recognition criteria occur, not cash timing alone.
• Going concern: assess and disclose the basis where the reporting framework requires it; do not promise future continuity.
• Consistency: avoid arbitrary policy shifts, but document justified changes and required disclosures.
• Prudence: use caution without intentional bias or hidden reserves.
• Materiality: assess nature and amount in context, not by a single universal threshold.

Substance, evidence and measurement

Accounting reports should represent the economic phenomenon and contractual rights or obligations relevant to the transaction. A label on an invoice is not always enough to establish the correct treatment. Review the contract, delivery evidence, control, payment terms and applicable standard. Measurement also involves judgment: cost, fair value, expected cash flows or another basis may be required depending on the item and framework. Estimates should identify data, method and uncertainty. A spreadsheet formula cannot determine a policy question on its own, and a polished explanation does not replace approval from a qualified responsible person.

Fictional examples: when a slogan is not enough

A fictional company buys equipment for operations and also pays for routine maintenance. A beginner may call both items assets because both support future work. The correct treatment cannot be decided by that phrase alone; the entity must apply the relevant standard's recognition and measurement criteria to the facts. In a second fictional case, an entity changes an estimate after receiving better information. Consistency does not prohibit updating an estimate when required, but the reason, data and period effect should be documented. The point is to move from slogan to evidence and applicable requirement.

For a simple classroom accrual, imagine a fictional vendor completes a ₹12,000 service before month-end but invoices the company later. The preparer would verify completion and contractual terms, then follow the entity's policy and applicable standards to determine whether an accrual is needed. The example deliberately does not prescribe journal accounts or tax treatment because those depend on facts, framework and policy. A reviewer should trace the estimate to a source, confirm period cut-off, assess duplicate invoices and reverse or settle it through the approved close process.

A safe way to use principles in day-to-day work

Start with the transaction and the question being answered. Identify the reporting framework and period, collect source records, find the relevant standard or policy, document assumptions, calculate the effect and obtain the required review. A preparation note should separate facts from judgments and estimates. If a process depends on a threshold, definition or rule that can change, cite its source date and owner. This is especially important in banking and finance operations, where reporting data may feed management information, regulatory returns and audited financial statements. Never treat an informal convention as permission to ignore a specific requirement.

1. Name the item, event, entity and reporting period.
2. Confirm which current framework and standard apply.
3. Gather contracts, invoices, source-system data and other relevant evidence.
4. Explain the recognition, measurement and presentation judgment with assumptions.
5. Reconcile the entry, retain reviewer evidence and disclose uncertainty when required.

How principles show up in a reporting review

A reviewer can use these concepts as questions, not as substitutes for a standard. Is the transaction recorded in the period when the relevant recognition criteria are met? Does the report faithfully represent the underlying rights and obligations? Are estimates based on current evidence? Is the method applied consistently to comparable items, and would a permitted change require disclosure? Could an omission or classification affect a user's decision? These prompts help organize review, but the applicable accounting requirement determines the answer. If the facts are complex, the preparer should consult the authorized accounting policy owner.

An audit trail should connect the conclusion to its evidence. A reviewer can inspect the contract, invoice or operational record, confirm the entity and period, trace the calculation and see who approved the treatment. Where an estimate is involved, retain assumptions and subsequent information relevant to the estimate. If evidence is missing, record the limitation and escalation rather than replacing it with a confident-sounding convention. This discipline is useful for students because it turns abstract words into practical documentation habits.

It is also important to distinguish accounting estimates from errors and policy changes. New information may change an estimate; discovering that a prior entry omitted available evidence may require an error assessment; and changing a policy follows defined requirements. Calling all three 'consistency issues' hides the difference. A learner should note the event, period, cause and applicable standard, then ask a qualified reviewer to determine the treatment. This article intentionally does not prescribe a journal entry for a real entity.

• Name the concept being applied and the reporting question it helps explain.
• Cite the relevant current standard rather than treating a textbook list as authority.
• Keep source evidence, assumptions and approval together with the workpaper.
• Explain any uncertainty and distinguish it from a verified accounting conclusion.
• Refresh learning notes when official standards or amendments change.

Frequently asked questions

Review ICAI's 2025–26 Ind AS compendium

Read the IFRS Conceptual Framework overview

Review the accounting basics resource

Explore financial accounting and banking concepts

Review accounting interview questions

Explore Finance Operations learning information

Ask the team about current program scope and terms

Read the financial reporting controls guide

Editorial note: reviewed 28 September 2026. This material is for general learning only; standards, amendments and entity policies change. Obtain qualified review for actual accounting treatment.