ESOP Accounting

The Problem

Accounting for employee stock option plans (ESOPs) begins with a document that is surprisingly hard to process at scale: the individual grant letter. A mid-market company issuing options to 80–300 employees across two or three grant cycles per year may generate hundreds of grant letters, each containing employee identifiers, grant dates, exercise prices, vesting schedules, and plan references that must be extracted, cross-checked against the plan document, and translated into periodic compensation expense entries. Done manually, a controller or stock-plan administrator typically spends two to four days per grant cycle keying data into a spreadsheet before any accounting can begin.

The regulatory obligation is firm. Under Ind AS 102 (Share-based Payment), the fair value of options must be determined at grant date and recognised over the vesting period on a systematic basis. The equivalent US standard, ASC 718 (Compensation — Stock Compensation), imposes the same measurement and recognition discipline. Both standards require that every grant record carry a defensible fair-value measurement, a correctly parsed vesting schedule, and an auditable forfeiture-rate assumption — none of which can be defaulted or estimated without the source document.

At scale the manual process breaks in predictable ways. Vesting schedules described in natural language — '25% after year one, remainder monthly' — are parsed inconsistently across grant cohorts, producing mismatched amortisation tables. Exercise prices denominated in USD for options issued by a foreign parent are sometimes carried at the wrong exchange rate. Repriced grants referencing an earlier grant ID are booked as new grants rather than modifications, understating or double-counting incremental fair value under Ind AS 102.26 or ASC 718-20-35-3. Each of these errors accumulates silently until the external auditor or internal audit function opens the equity footnote workpaper.

Why It Matters: Context

Ind AS 102 and ASC 718 are not optional disclosures — they determine the income-statement charge for every period in which unvested options exist. Ind AS 102.12 requires that, for equity-settled awards, the entity measure fair value at grant date using an option-pricing model (typically Black-Scholes-Merton or a binomial lattice) and recognise that amount as an expense over the vesting period, adjusted for estimated forfeitures under Ind AS 102.19. ASC 718 mirrors this structure, with the ASU 2016-09 practical expedient allowing US entities to recognise forfeitures as incurred rather than estimating them upfront. In either regime, the accounting engine can only be as accurate as the structured data extracted from the source grant letter.

For mid-market companies — those with 50 to 500 active option holders and no dedicated equity-compensation system — the grant letter is almost always a PDF or Word document produced by HR or legal counsel. There is no single-source-of-truth register automatically fed into the GL. Controllers must manually reconcile grant letters against plan documents approved by the board, verify that the cited plan name and board-approval date precede the grant date (a governance requirement), and maintain a live table of unexercised, forfeited, and expired options for each reporting period. This is tractable for a single cohort; it becomes error-prone across five or six cohorts with different exercise prices and vesting ladders.

Failure takes concrete forms. An incorrectly parsed cliff-versus-graded vesting schedule produces a front-loaded or back-loaded expense that misstates employee benefits cost in interim filings. A repriced grant booked as a new grant overstates the option pool on the cap table and inflates stock-based compensation expense, both of which draw audit findings. Under ICAI SA 505 (External Confirmations) and standard equity-footnote audit procedures, auditors routinely confirm grant terms directly with the plan administrator — discrepancies between the confirmed terms and the ledger entries can result in an adjusting journal entry requirement or, in material cases, a qualified audit opinion on the financial statements.

What This Workflow Automates

1. Cadel ingests each ESOP grant letter (PDF or Word) and extracts structured fields: employee name, employee ID, grant date, number of options, exercise price, currency, vesting schedule, cliff date, plan name, and plan version identifier.
2. The extracted vesting schedule is parsed against a controlled vocabulary of schedule types — cliff, graded, cliff-plus-graded hybrid — and any ambiguous natural-language description is flagged as requiring controller sign-off before the amortisation table is generated, preventing silent misclassification under Ind AS 102.12 or ASC 718-10-55-68.
3. Where an exercise price is denominated in a currency other than the entity's functional currency, the workflow identifies the mismatch, attaches the applicable RBI reference rate (or FRED mid-market rate for USD-functional entities) for the grant date, computes the converted amount, and marks the field for treasury review under Ind AS 21.
4. For any grant letter that references an earlier grant ID — indicating a repricing or modification — the workflow links the amendment to the original grant record, computes the incremental fair-value delta, and generates a separate accounting line dated to the modification date, satisfying the incremental-charge requirement under Ind AS 102.26 or ASC 718-20-35-3.
5. The cited plan identifier is cross-checked against the registered plan document library; grants referencing a plan not present in the library, or whose board-approval date post-dates the grant date, are blocked from posting and marked as 'unresolvable' pending attachment of a valid plan document.
6. Where no forfeiture rate has been configured at the plan level, the workflow raises a validation warning, prompts the preparer to enter a historically or actuarially supported rate, and records the assumption in the audit workpaper export — preventing the silent default to zero forfeiture that would overstate compensation cost.
7. In multi-entity groups, the workflow enforces a compound key of entity-code plus grant-ID at ingestion, surfaces all collisions with entity attribution, and blocks posting until duplicate IDs are disambiguated, preventing double-counting at the consolidation layer.

All seven steps execute within seconds of document upload, producing a deterministic, field-level output record for every grant letter that any controller can inspect, annotate, and attach to the period-close equity workpaper without further manual transcription.

Edge Cases We Simulate

The workflow ships with a battery of synthetic test scenarios that exercise every failure mode we have seen in real-world data. Each scenario produces a deterministic outcome that an auditor or controller can verify in seconds.

Sample Documents

Download or inspect the seeded sample files used to demonstrate this workflow:

Sample Results

In a representative processing run across a cohort of grant letters spanning three ESOP plan vintages, Cadel extracts all required structured fields — employee ID, grant date, exercise price, vesting schedule type, plan reference — with field-level extraction validated against the source document. Validation checks covering plan-reference integrity, currency denomination, vesting-type classification, and forfeiture-rate configuration produce pass or actionable-warning outcomes for each grant record, with no grant advancing to the amortisation-table stage until all hard-stop validations are cleared. Across a typical 100-grant cohort, controllers report that data entry time falls from approximately two working days to under 20 minutes, with zero manual re-keying of exercise prices or vesting terms into the compensation-expense model.

A specific exception class that the workflow catches with high consistency is the cliff-plus-graded hybrid vesting schedule described in ambiguous language: for example, a letter stating 'vests as to 25% on the first anniversary of the grant date and as to 1/48th per month thereafter' is correctly identified as a hybrid — not a pure graded schedule — which changes the shape of the Ind AS 102 amortisation curve and, over a four-year vesting period on a ₹50 lakh grant, produces a materially different front-year expense charge than the pure-graded misclassification would generate. Without automated parsing, this class of error typically goes undetected until the auditor reconstructs the vesting table from the original letter.

Why Automation Wins Here

For a mid-market company running two to four ESOP grant cycles annually across 100–300 option holders, the workflow reduces grant-data preparation time from two to three working days per cycle to under 30 minutes, while eliminating the six deterministic error classes — vesting misclassification, FX omission, modification misposting, invalid plan references, missing forfeiture assumptions, and duplicate grant IDs — that most commonly generate audit findings or income-statement restatements in equity-compensation accounting. The reduction is structural, not dependent on preparer experience: every extraction and validation rule runs identically across every grant letter, every cycle.

The output artifact is a structured grant register in CSV and PDF formats, with field-level source citations back to the original grant letter, a validation-result column for each check, and the forfeiture-rate assumption documented inline. This register drops directly into the controller's period-close audit file as the supporting schedule for the stock-based compensation footnote, satisfying the documentation expectations of external auditors performing procedures under ICAI SA 230 (Audit Documentation) or PCAOB AS 1215 without any reformatting or supplemental annotation.

Frequently Asked Questions