Materiality in startup audits: why your auditor doesn't care about your ₹50 lakh receivable

Every audit season we get the same call from a founder. The auditors have flagged a ₹50 lakh balance that the founder considers immaterial — a stale receivable, a minor accrual, a reclassification dispute. The founder wants us to push back. Sometimes we do. More often we explain why the auditor's response is not about ₹50 lakh at all. It is about what a ₹50 lakh item signals when the materiality threshold is sitting at ₹4 crore.

Materiality is the most misunderstood number in any audit. Founders treat it like a tolerance band — anything below it is forgivable. Auditors treat it like a measuring stick — items below it are not automatically forgivable, they are just measured differently. The gap between those two views is where most audit disputes happen.

How materiality actually gets set

SA 320 — Materiality in Planning and Performing an Audit — gives the auditor a framework but not a formula. The standard says materiality should be set at a level where misstatements, individually or in aggregate, could reasonably be expected to influence the economic decisions of users of the financial statements.

In practice, that translates to a benchmark and a percentage. The benchmark depends on the company. Profit before tax for profitable companies. Revenue for loss-making startups. Equity or total assets for asset-heavy businesses like NBFCs or real-estate platforms.

The percentages most Indian audit firms work to: 5% of profit before tax, 0.5% to 1% of revenue, 1% to 2% of equity, 0.5% of total assets. These are not codified in SA 320. They are firm-level conventions tested over decades of audit work and broadly accepted by NFRA and ICAI peer reviewers.

For a Series B startup with ₹500 crore revenue and ₹80 crore loss, profit-based materiality fails — you cannot take 5% of a negative number and call it material. So the auditor uses revenue. At 0.5% of ₹500 crore, that is ₹2.5 crore. At 1%, ₹5 crore. The audit team will document why they picked one end of the range. Most settle around ₹3-4 crore for a company of that size.

Now your ₹50 lakh receivable. It is one-eighth of materiality. Below the line.

Why a sub-materiality item still gets flagged

This is the part founders miss. Materiality is the threshold at which an individual misstatement becomes reportable as a misstatement. It is not the threshold at which the auditor stops caring.

Two layers sit underneath overall materiality.

Performance materiality is typically set at 75% of overall materiality. So if your overall materiality is ₹4 crore, performance materiality is ₹3 crore. This is the threshold used at the account-balance and transaction-class level — receivables, revenue, payroll. The auditor designs sample sizes and testing depth against performance materiality, not overall materiality. The 25% buffer is for undetected misstatements that aggregate up.

Clearly trivial threshold — the judgmental misstatement floor — is typically 5% of overall materiality. For our ₹4 crore example, that is ₹20 lakh. Misstatements above ₹20 lakh go into the schedule of uncorrected misstatements. Below ₹20 lakh, they get noted in the working papers but not aggregated for opinion purposes.

Your ₹50 lakh receivable sits between the trivial threshold and overall materiality. It goes into the schedule of uncorrected misstatements. At year-end, the auditor aggregates everything in that schedule. If the aggregate crosses overall materiality, the opinion gets modified. If it does not, the items still get reported to the audit committee in the management letter.

So the auditor is not arguing that ₹50 lakh on its own moves the opinion. The auditor is keeping score.

When sub-materiality items become a bigger problem

There is a second reason that ₹50 lakh receivable gets flagged. SA 240 — Auditor's Responsibilities Relating to Fraud — requires the auditor to consider whether a misstatement, even below materiality, is an indicator of a control failure or a fraud risk.

An aged receivable from a customer the company stopped invoicing eight months ago is a control failure. Either the credit-control process did not flag it, or it was flagged and ignored. Either way, the auditor will write it up — not because of the ₹50 lakh, but because of what it says about the receivables management process. If the company has 30 such items totalling ₹15 crore, the auditor now has a control finding for the audit report under Section 143(3)(i) — internal financial controls.

The pattern matters more than the number. A single ₹50 lakh stale receivable is a housekeeping item. Thirty of them is a control-environment issue. The auditor is not pricing the receivable. The auditor is pricing the process that let it become stale.

What founders should actually argue about

The productive conversation with an auditor about materiality is not 'this item is too small.' It is about the benchmark and the percentage.

If your company has just turned profitable after three years of losses, the auditor may still be using revenue as the benchmark out of habit. Ask whether profit before tax is now the more appropriate measure. If yes, materiality drops by an order of magnitude — sometimes that helps you, sometimes it does not, but at least you understand which way the number moves.

If you are an asset-heavy business — say a logistics company with ₹400 crore of warehouse assets and ₹200 crore of revenue — argue for total assets as the benchmark. The audit firm's risk model may default to revenue, but for a balance-sheet-driven business that under-states what users of the statements actually care about.

If the audit is for a fundraise where investors are looking at unit economics, you can flag that revenue-based materiality misses the place where the most diligence will land — gross margin. The auditor still sets materiality at the financial-statement level, but they can scope additional procedures around gross margin reconciliations. That conversation is more productive than arguing about a ₹50 lakh receivable.

The disclosure problem

Ind-AS 1 requires that material items be disclosed separately. The auditor's materiality drives that disclosure. A receivable that is below materiality individually but represents 20% of total receivables may still need separate disclosure because of concentration. A loan to a related party at ₹40 lakh — below materiality on its own — has to be disclosed under Ind-AS 24 because the related-party concept overrides quantitative materiality.

Founders sometimes ask whether they can avoid disclosure by keeping items below the materiality line. They cannot. Materiality drives the audit opinion. It does not drive the disclosure standard. A non-disclosure that would mislead a user is reportable regardless of size.

What a sensible materiality conversation looks like

Before fieldwork starts, ask your auditor for the planning memo. Materiality is documented there. You should see: the benchmark chosen, the percentage applied, the overall materiality number, the performance materiality, and the trivial threshold.

Read the four numbers. Ask why each was picked. If the audit team cannot defend the benchmark choice without referring to last year's working paper, that is a warning. Audit work is supposed to be re-evaluated each year against the current business profile.

Once you have those numbers, you can predict 80% of the audit's depth. The sample sizes for receivables and payables flow from performance materiality. The journal-entry testing threshold flows from the trivial threshold. The opinion-level issues flow from items aggregated above performance materiality.

The ₹50 lakh receivable arguments mostly stop after that conversation. Either the item is part of a pattern the auditor cares about, in which case the founder fixes the process, or it is genuinely a one-off and goes into the SUM schedule to be aggregated and ignored.

Either way, you stop arguing about the number and start managing the process that produces the number. That is what materiality is meant to do.