Revenue Recognition Fraud: Ind AS 115 Red Flags & Detection

Why Revenue Is the Primary Fraud Target

Revenue occupies a unique position in financial reporting — it is the top line that drives virtually every financial metric. Earnings, margins, valuations, loan covenants, management compensation, and market expectations all flow from revenue. This creates intense pressure to meet or exceed revenue expectations, making revenue recognition the most fertile ground for financial statement fraud.

SA 240 (The Auditor’s Responsibilities Relating to Fraud in an Audit of Financial Statements) recognises this reality by establishing a rebuttable presumption under Para 26 that revenue recognition involves a risk of fraud. This means that in every audit engagement, the auditor must either design specific fraud response procedures for revenue recognition or document why the presumption has been rebutted — a high bar that requires specific facts and circumstances.

At our forensic accounting practice, revenue manipulation accounts for the largest category of financial statement fraud cases we investigate. The fraud schemes have become increasingly sophisticated under Ind AS 115, exploiting the judgements inherent in the five-step model.

Ind AS 115 — The Five-Step Model and Fraud Vulnerabilities

Step 1: Identify the Contract — Fraud at the Contract Level

Ind AS 115 requires that a contract exists with commercial substance, the parties have approved it, each party’s rights and payment terms are identifiable, and it is probable that the entity will collect the consideration. Fraud vulnerabilities at this step include:

Fictitious contracts: Creating contracts with non-existent or non-arm’s length customers. This may involve related party entities (see our related party fraud guide), shell companies, or entities that are unaware of the purported contract.

Side agreements: The formal contract shows a sale, but undisclosed side agreements provide the customer with unconditional return rights, consignment-like arrangements, or contingencies that negate the commercial substance of the contract. The revenue is recorded based on the formal contract while the side agreement ensures no genuine economic transaction has occurred.

Contract modification manipulation: Ind AS 115 has specific rules for contract modifications — whether they are treated as separate contracts or as modifications of existing contracts affects revenue timing and amount. Fraudulent modification of contract terms can accelerate or inflate revenue recognition.

Step 2: Identify Performance Obligations — Bundling and Unbundling Manipulation

A performance obligation is a promise to deliver a distinct good or service. The identification of performance obligations affects how revenue is allocated and when it is recognised. Fraud vulnerabilities include:

Improper bundling: Combining multiple performance obligations into a single obligation to accelerate revenue recognition. For example, a software company that sells a licence with implementation services may improperly treat the entire arrangement as a single obligation, recognising all revenue upon software delivery rather than over the implementation period.

Improper unbundling: Splitting a single performance obligation into multiple obligations to accelerate partial revenue recognition. For example, splitting a construction contract into “design” and “construction” components and recognising the “design” revenue upfront when the design is substantially part of the construction obligation.

Step 3: Determine Transaction Price — Variable Consideration Manipulation

The transaction price includes fixed consideration and estimated variable consideration (discounts, rebates, returns, incentives, penalties). This step involves significant estimation judgements that are susceptible to fraud:

Overestimating transaction price: Understating expected returns, discounts, and rebates to inflate the net transaction price. Companies may use unrealistically low return estimates or ignore historical discount patterns to record higher revenue.

Constraining variable consideration: Ind AS 115 requires that variable consideration be included only to the extent it is highly probable that a significant reversal will not occur. Fraudulent application involves including variable consideration that does not meet this threshold.

Financing component manipulation: Significant financing components in contracts (payment terms exceeding 12 months) require adjustment to the transaction price. Failure to identify or properly account for financing components can inflate revenue.

Step 4: Allocate Transaction Price — Stand-alone Selling Price Manipulation

When a contract has multiple performance obligations, the transaction price is allocated based on relative stand-alone selling prices. Fraud involves manipulating stand-alone selling price estimates to front-load revenue allocation to obligations that are satisfied earlier.

Step 5: Recognise Revenue — Timing Manipulation

Revenue is recognised either at a point in time (when control transfers) or over time (as performance obligation is satisfied). This is the most common area of revenue fraud:

Premature point-in-time recognition: Recording revenue before control has transferred — shipping goods to a warehouse rather than the customer, recording revenue on bill-and-hold arrangements without meeting Ind AS 115 criteria, or backdating shipping documents.

Over-time recognition manipulation: For contracts recognised over time (using input or output methods), manipulating the measure of progress to accelerate revenue. In construction contracts, this commonly involves overstating the percentage of completion by inflating costs incurred (input method) or overstating the work completed (output method).

Common Revenue Fraud Schemes in India

Channel Stuffing

Channel stuffing involves pushing excessive inventory to distributors or channel partners near the end of a reporting period. The goods are shipped and invoiced, but the sales are not genuinely driven by end-customer demand. Distributors accept the excess inventory because of extended payment terms, return guarantees, or pricing incentives — none of which may be disclosed.

Detection techniques:

• Revenue concentration analysis — what percentage of quarterly revenue is recorded in the last month or last week?
• Sales return and credit note analysis — do returns spike in the first month of the next quarter?
• Distributor inventory analysis — are distributor inventory levels increasing faster than end-customer sales?
• Correlation between revenue timing and shipment/delivery dates
• Analysis of payment terms offered near period-end versus normal terms

Circular Trading (Round-Tripping)

Goods or services are traded in a circular pattern between related or colluding entities, with each transaction recorded as revenue. No genuine economic activity occurs — the same goods may physically remain in the same location. This scheme is particularly common in commodities, chemicals, and trading sectors.

Detection techniques:

• Counterparty analysis — are the same entities simultaneously customers and vendors?
• Physical verification — can goods movements be verified through transport documentation, weighbridge records, and warehouse receipts?
• Net settlement analysis — are transactions with specific counterparties settling on a net basis rather than gross?
• GST verification — does the GSTR-2B data corroborate the purchase invoices from the counterparty?

Bill-and-Hold Revenue

The company invoices the customer but retains physical possession of the goods, claiming the customer has requested delayed delivery. Ind AS 115 permits bill-and-hold revenue only when specific criteria are met — the arrangement must have commercial substance, the goods must be separately identified as belonging to the customer, the goods must be currently ready for transfer, and the entity cannot use the goods or direct them to another customer.

Detection techniques:

• Physical verification of bill-and-hold inventory — are the goods segregated and identified?
• Customer confirmation — did the customer request the bill-and-hold arrangement?
• Subsequent delivery analysis — were the goods actually delivered to the customer?
• Pattern analysis — is bill-and-hold revenue concentrated near period-end?

Percentage-of-Completion Manipulation

For long-term construction and infrastructure contracts recognised over time, manipulating the percentage of completion inflates revenue. Common manipulation techniques include overstating costs incurred (input method), inflating physical completion estimates (output method), and deferring the recognition of expected losses on unprofitable contracts.

Detection techniques:

• Independent physical verification of project completion against reported percentage
• Cost analysis — are costs being accelerated through fictitious vendor invoices or premature cost recognition?
• Budget-to-actual comparison — are project budgets being revised upward to justify higher completion percentages?
• Margin analysis — are margins on individual contracts consistent across periods, or do they show unusual patterns?

Consignment Disguised as Sales

Goods sent on consignment (where revenue should be recognised only upon sale to the end customer) are recorded as outright sales to the consignee. The consignee has the right to return unsold goods, but this right is not reflected in the accounting.

Data Analytics for Revenue Fraud Detection

At Virtual Auditor, we deploy the following analytical techniques in revenue fraud investigations:

Period-end revenue spike analysis: We calculate the percentage of quarterly or annual revenue recorded in the final days or weeks of the period. A disproportionate concentration (significantly exceeding the normal daily run rate) indicates potential manipulation — either channel stuffing, premature recognition, or fictitious transactions.

Revenue-cash flow divergence: Genuine revenue growth should eventually translate into operating cash flow growth. When reported revenue grows but operating cash flow stagnates or declines, it suggests that revenue may not be translating into cash collections — a strong indicator of fictitious or premature revenue. We track the revenue-to-operating cash flow ratio over multiple periods.

Days sales outstanding (DSO) trend: Rising DSO (receivables growing faster than revenue) indicates that revenue is being recorded but not collected. This is consistent with channel stuffing (extended payment terms), fictitious sales (no customer to collect from), or premature recognition (customer disputes the timing).

Benford’s Law analysis: First-digit distribution analysis on invoice amounts. A natural distribution of transaction amounts follows Benford’s Law — deviations suggest artificial creation of invoices, particularly when certain amounts cluster around round numbers or just below approval thresholds.

Credit note and return analysis: We analyse credit notes and sales returns in the periods immediately following revenue recognition — a spike in Q1 reversals of Q4 revenue is a classic indicator of channel stuffing or fictitious period-end sales.

Customer concentration analysis: Revenue concentration in a small number of customers, particularly new customers or customers with related party characteristics, warrants deeper investigation. We cross-reference customer data with the related party universe identified through our fraud risk assessment framework.

SA 240 Requirements for Revenue Fraud Risk

Auditors performing statutory audits under SA 240 must:

• Evaluate fraud risk factors related to revenue recognition — including management incentives (bonuses, targets), industry conditions (competitive pressure, declining demand), and opportunity factors (complex revenue arrangements, significant estimates)
• Perform inquiry of management regarding their assessment of the risk that financial statements may be materially misstated due to revenue fraud
• Design audit procedures responsive to the assessed fraud risk — including substantive analytical procedures, test of details on revenue transactions, and evaluation of revenue recognition policies
• Test journal entries and other adjustments for evidence of revenue manipulation — particularly manual entries, entries posted near period-end, and entries with unusual characteristics
• Document the basis if the presumption of revenue fraud risk is rebutted — this requires specific facts and circumstances demonstrating why revenue recognition is not a fraud risk for the particular entity

Where the statutory auditor identifies fraud or suspects fraud, the reporting obligations under Companies Act Section 143(12) apply — fraud above Rs 1 crore must be reported to the Central Government, and fraud below Rs 1 crore must be reported to the audit committee. Additionally, CARO 2020 clause (xi) requires the auditor to report whether fraud has been noticed or reported during the year.

Industry-Specific Revenue Fraud Risks

IT Services and Software

Time-and-material contracts — inflating effort hours; fixed-price contracts — overstating percentage of completion; licence revenue — premature recognition before delivery; SaaS revenue — recognising multi-year contracts upfront instead of over the subscription period.

Real Estate and Construction

Percentage-of-completion manipulation; recognising revenue on advance bookings before construction completion; failure to recognise contract losses; inflating project costs to justify higher completion percentages. This sector is particularly susceptible given the long project durations and significant estimates involved.

FMCG and Consumer Goods

Channel stuffing to distributors; trade scheme manipulation (understating discounts and rebates); consignment sales recorded as outright sales; secondary sales not verified against primary sales data.

Pharmaceuticals

Product return manipulation; free goods and samples not properly excluded from revenue; contract manufacturing revenue timing; licensing revenue and milestone recognition judgements.

Financial Services

Fee income timing; interest income recognition on stressed assets (NPA classification avoidance); insurance premium recognition; processing fee amortisation versus upfront recognition.

Regulatory and Legal Consequences

Revenue recognition fraud triggers multiple regulatory consequences in India:

SEBI enforcement: For listed companies, revenue misstatement is a violation of LODR regulations requiring true and fair financial statements. SEBI can impose penalties, disgorgement of profits, and debarment of directors. SEBI PFUTP regulations may also apply if the revenue fraud affected share prices.

Companies Act consequences: Section 447 defines fraud with punishment of imprisonment from 6 months to 10 years and fine from the amount involved to three times the amount involved. Revenue fraud affecting financial statements directly falls within this provision. SFIO investigation may be ordered under Section 212.

Income tax implications: Revenue overstatement results in overpayment of income tax. While this may seem to benefit the Revenue, the restated financials may trigger reassessment proceedings under Section 147/148 and create complications for carryforward of losses or MAT credit.

GST implications: Fictitious sales generate GST liability. If the corresponding purchases are also fictitious, the arrangement may constitute a circular trading scheme for GST input tax credit fraud — a serious offence under GST Section 132.

Frequently Asked Questions

What is revenue recognition fraud?

Revenue recognition fraud involves deliberately manipulating the timing, amount, or existence of revenue to misstate financial performance. Under Ind AS 115, revenue is recognised when performance obligations are satisfied and control transfers to the customer. Fraud occurs when revenue is recorded before these conditions are met, fictitious revenue is created, or revenue is improperly classified.

Why does SA 240 presume fraud risk in revenue recognition?

SA 240 Para 26 establishes this presumption because revenue is the largest income statement item, directly drives valuations and performance targets, involves significant judgements, and has historically been the most common subject of financial statement fraud globally. The presumption can be rebutted only with documented specific facts and circumstances.

What is the difference between aggressive accounting and fraud?

Aggressive accounting involves applying judgements within the boundaries of accounting standards in a manner that maximises reported results — it is at the edge of acceptable practice. Fraud involves deliberately misapplying standards, creating fictitious transactions, or concealing information to deceive financial statement users. The line between the two can be thin, but the intent to deceive distinguishes fraud from aggressive accounting.

Can Ind AS 115 transition itself create fraud risk?

Yes. The transition from Ind AS 18/11 to Ind AS 115 created opportunities for manipulation — particularly in the identification of performance obligations (which affects allocation and timing) and in the transition adjustments themselves. Companies had to apply significant judgement during transition, and some may have structured transition choices to inflate or smooth revenue.

How does forensic investigation of revenue fraud differ from a statutory audit?

Statutory audit tests revenue recognition for material misstatement with reasonable assurance. Forensic investigation is specifically designed to detect fraud — using investigative techniques (not just audit procedures), full population data analytics (not sampling), external verification (customer confirmations, shipping records, independent market data), and structured interviews. Forensic investigation also produces reports admissible as evidence in legal proceedings, which statutory audit work papers are not designed to be.