ASC 842 Lease Accounting for Mid-Market: The Implementation Playbook Nobody Hands You

The state of mid-market ASC 842 implementations The Financial Accounting Standards Board issued ASU 2016-02, codified as ASC 842, in February 2016 with an original effective date for public companies of fiscal years beginning after December 15, 2018, and for private companies after December 15, 2019. The private-company effective date was deferred twice, first by ASU 2019-10 and then by ASU 2020-05, landing at fiscal years beginning after December 15, 2021. The standard is now in effect for every mid-market private company that prepares GAAP financials, and has been for four reporting cycles. The pattern across the mid-market firms whose lease accounting we have audited in the last two years is consistent. The firm implemented ASC 842 in the first applicable year, often with the help of an external consultant or the audit firm's advisory practice. A spreadsheet was built. The right-of-use assets and lease liabilities were recorded as of the transition date. The journal entries were posted. The audit closed. And then the implementation was, in effect, abandoned. The lease subledger lives in a spreadsheet that has not been updated since the implementation year. New leases entered into in subsequent years were not added to the subledger. Modifications to existing leases were not re-measured. The discount rate selected at transition has not been re-evaluated. Embedded leases in IT and equipment contracts entered into in the post-transition years were not identified. The next audit is going to find this. The auditor's lease-accounting testing in year four of the standard is no longer a transition test; it is a substantive test of the current-period balances and the rollforward of activity since the prior year-end. The mid-market firms that did not maintain the implementation as an operational practice produce findings that compound across periods: missed leases, stale discount rates, modification accounting errors, ROU asset balances that do not reconcile to the lease subledger because the subledger has not kept pace with the activity. This guide walks through what ASC 842 actually requires in steady state, the data and software decisions that determine whether the implementation is sustainable, the audit-ready evidence the controller needs to maintain, and the post-implementation review patterns we see most often when the firm engages us to clean up an implementation that has drifted. What the standard actually requires ASC 842 replaced the prior lease-accounting standard (ASC 840) and made two structural changes. The first is the recognition of essentially all leases on the balance sheet as a right-of-use asset and a corresponding lease liability. Under the prior standard, operating leases were off-balance-sheet, with only rent expense flowing through the income statement; under ASC 842, the operating lease produces a ROU asset, a lease liability, straight-line lease expense, and a lessee disclosure footnote that walks the maturity analysis. The second is the elimination of the bright-line tests for capital-versus-operating classification under ASC 840, replaced by a principles-based classification framework that distinguishes finance leases (which produce front-loaded interest and amortization expense) from operating leases (which produce straight-line lease expense). The mechanics for a typical operating lease are: identify the lease term, determine the lease payments (including any reasonably certain renewal periods, residual value guarantees, and purchase options), select the discount rate (the rate implicit in the lease if readily determinable; otherwise the lessee's incremental borrowing rate, with a private-company practical expedient under ASU 2018-11 to use a risk-free rate, applied at the asset-class level), calculate the present value of the lease payments to determine the lease liability, and record a ROU asset equal to the lease liability plus prepaid lease payments minus lease incentives received. Each subsequent period, the lease liability accretes interest at the discount rate, the lease payment reduces the liability, and the ROU asset is amortized in a way that produces straight-line lease expense (for operating leases) or front-loaded expense (for finance leases). At each period-end, the controller produces a rollforward of the ROU asset and the lease liability that ties to the GL. The standard also requires a comprehensive lessee disclosure: the components of lease cost (operating, finance amortization, finance interest, short-term, variable, sublease income), the weighted-average remaining lease term and discount rate by lease class, a maturity analysis of lease liabilities for each of the next five years and thereafter, and supplemental cash flow information. The disclosure is built from the lease subledger. If the subledger is incomplete or stale, the disclosure is wrong. Two practical expedients matter most for mid-market private companies. The first is the package of practical expedients available at transition (which most firms elected): an entity is not required to reassess whether expired or existing contracts contain leases, the classification of expired or existing leases, or initial direct costs for any existing leases. The second is the ongoing practical expedient available to private companies under ASU 2018-11 and clarified by ASU 2021-09: use the risk-free rate as the discount rate, applied at the asset-class level (not the lease level), as an alternative to the incremental borrowing rate. The risk-free rate is operationally simpler but produces a higher present value of lease payments and a larger ROU asset and liability than an IBR-based calculation. The election is documented in the lease policy and disclosed in the footnote. The data collection that determines everything else The single most important success factor in an ASC 842 implementation is the quality of the underlying lease inventory. Every lease has to be identified, abstracted, and loaded into whatever system the firm chooses to maintain its lease subledger. The mid-market firms that fail this step produce implementations that are wrong from inception and remain wrong forever; the firms that succeed treat lease abstraction as a controlled procedure with a defined output. The lease inventory begins with the obvious leases: real estate, vehicle fleets, large equipment. The hard part is the embedded leases: the IT contracts that include dedicated hardware (servers, networking equipment, point-of-sale terminals), the manufacturing arrangements that include dedicated machinery, the logistics arrangements that include dedicated trailers or containers, the cloud-services contracts that include dedicated infrastructure (less common after ASU 2018-15 narrowed the scope, but still present in some cases). Under ASC 842-10-15, a contract contains a lease if the contract conveys the right to control the use of an identified asset for a period of time in exchange for consideration. The "identified asset" criterion is satisfied when the asset is explicitly or implicitly specified, and the supplier does not have a substantive substitution right. The "right to control" criterion requires both the right to obtain substantially all the economic benefits and the right to direct the use of the asset. The pattern we see most often is that real estate leases are identified, vehicle leases are identified, and embedded leases are missed entirely. The IT services contract that includes a dedicated server array sitting in the firm's data center, with the supplier providing maintenance but no substitution right, is a lease under ASC 842 even though the contract is titled "managed services agreement" and the payment is described as a service fee. The auditor finds these by sampling material service contracts and reading them; the controller should find them first by running an embedded-lease scan against every service contract entered into in the period. The lease abstraction itself is mechanical. For each lease, the controller documents the asset description and location, the lessor and contract reference, the commencement date and lease term (including any reasonably certain renewal options), the payment schedule (including any escalations, free-rent periods, and variable components), the discount rate used and the basis for it (incremental borrowing rate at commencement with documented derivation, or risk-free rate under the practical expedient with documented selection), the classification (operating or finance) with the documented analysis, any lease incentives received, any residual value guarantees, and any purchase options. The abstract is the foundation of the calculation; if the abstract is wrong, every subsequent calculation is wrong. For embedded leases, the abstract also documents the allocation of contract consideration between the lease component and the non-lease components (typically the service fees). Under ASC 842-10-15-28 through 15-32, lessees must allocate consideration to lease and non-lease components based on relative standalone prices, unless the lessee elects the practical expedient to combine lease and non-lease components by class of underlying asset, in which case the entire arrangement is accounted for as a lease. Mid-market firms typically elect the combined practical expedient because the standalone-price allocation is operationally heavy and the difference in financial statement impact is rarely material. The election is documented in the lease policy. Software selection: what each tool is good at Mid-market firms have four practical options for the lease subledger. The choice is consequential because it determines the workflow, the audit evidence, and the cost of ongoing maintenance. Spreadsheet-based subledger. Acceptable for firms with fewer than fifteen leases, no embedded leases, and a controller who is willing to maintain the spreadsheet personally. The advantages are zero software cost and complete transparency; the disadvantages are formula fragility, no built-in modification accounting, and audit evidence that depends on the spreadsheet's version history. We see spreadsheet implementations break in the second or third year, when a modification has to be re-measured and the spreadsheet's logic does not handle it cleanly. For firms with more than fifteen leases or any embedded leases, the spreadsheet approach is not sustainable. LeaseQuery. The dominant mid-market tool, acquired by FinQuery, with a strong user base in private companies under five hundred million in revenue. Strengths: lease abstraction wizard, automated journal entry generation, modification handling, disclosure-ready reports, integration with major ERPs (NetSuite, Sage Intacct, Microsoft Dynamics, Oracle, Workday). Weaknesses: pricing is per-lease and rises with lease count; the disclosure outputs require some configuration to match the firm's specific footnote format. The implementation timeline is typically six to ten weeks for a mid-market firm with thirty to one hundred leases. Visual Lease. Comparable to LeaseQuery in feature scope, with stronger real-estate-specific features (CAM reconciliation, property-level reporting) for firms whose lease portfolio is predominantly real estate. Pricing is similar. The implementation timeline is similar. NetLease by Netgain. A NetSuite-native lease accounting application built as a SuiteApp, which means it operates inside the NetSuite environment and posts directly to the NetSuite GL. The advantage for NetSuite shops is operational integration: no separate system, no data export, no reconciliation between the lease subledger and the GL. The disadvantage is that the application is less mature than LeaseQuery and Visual Lease, and the disclosure outputs require more manual assembly. For NetSuite-based firms with twenty to one hundred leases, NetLease is often the right answer; for firms with more than one hundred leases or significant embedded-lease complexity, the dedicated tools are usually better. NetSuite Lease Management (the native Oracle/NetSuite module, distinct from NetLease). Available as part of the NetSuite SuiteApp ecosystem, with the advantage of native integration but more limited functionality than the dedicated tools. We see this work for simpler portfolios and break down for complex ones. CoStar Lease Manager. An option for firms whose lease portfolio is primarily real estate and who already use CoStar for property data. Less commonly selected for mid-market firms because the software is real-estate-focused and does not handle equipment or IT leases as cleanly. The decision framework we apply in client engagements is: under fifteen leases, no embedded-lease complexity, and a stable portfolio means a spreadsheet is acceptable but documented; fifteen to one hundred leases or any embedded-lease complexity means a dedicated tool (LeaseQuery, Visual Lease, or NetLease for NetSuite shops); over one hundred leases or significant real-estate concentration means LeaseQuery, Visual Lease, or CoStar with a dedicated lease accountant maintaining the subledger as a quarter-time function. The selection is documented in the lease policy and reviewed every two years. Audit-ready evidence: what the auditor will pull The auditor's lease-accounting testing in steady state targets four areas, and the controller's evidence pack should be built to satisfy each. The first is completeness: did the firm identify every lease? The auditor tests by sampling material service contracts, equipment purchase orders, and real estate transactions in the period and reading them for embedded-lease characteristics. The controller's evidence is the embedded-lease scan procedure: a documented checklist applied to every new contract over a defined dollar threshold, with the controller or designee signing off that the contract has been reviewed for lease characteristics and either added to the lease subledger or documented as not containing a lease. The scan is part of the contract-execution workflow, not a year-end reconciliation. Auditors who find embedded leases the controller missed expand the sample and propose adjustments. The second is lease abstraction accuracy: do the abstracts in the lease subledger match the underlying contracts? The auditor samples leases, typically a higher proportion of newer leases and leases that have been modified, and traces every input on the abstract to the contract: term, payments, escalations, options, classifications. The controller's evidence is the abstract itself, the contract referenced, and a peer-review sign-off documenting that a second person verified the abstract against the contract before it was loaded into the subledger. The third is calculation accuracy: do the journal entries, the ROU rollforward, and the disclosure tie to the abstracts and the calculations? The auditor recalculates a sample of leases, present value of payments, ROU and liability balances at period-end, current-period interest accretion, current-period amortization, and compares to the system output. The controller's evidence is the system's calculation reports, the underlying inputs (discount rate selection memo, classification analysis), and a tie-out from the lease subledger total to the GL ROU and lease liability balances. The tie-out is part of the audit-ready trial balance package and runs every period. The fourth is modification and remeasurement accounting: when leases were modified during the period, was the modification accounted for correctly? Under ASC 842-10-25-8 through 25-13, a lease modification is accounted for as a separate new lease (if the modification grants an additional right of use and the consideration increases commensurately) or as a remeasurement of the existing lease (in all other cases). Remeasurement requires re-measuring the lease liability using a current discount rate and adjusting the ROU asset by the same amount. The auditor tests every modification in the period. The controller's evidence is a modification log: every amendment to every lease, the date, the change, the analysis (separate lease vs. remeasurement), the recalculated balances, and the journal entry. The log is reviewed quarterly with the controller signing off. The post-implementation review patterns we see most often When we are engaged to review an existing ASC 842 implementation, we run a five-area diagnostic. The findings cluster around the same patterns nearly every time. Missed embedded leases. The implementation team focused on real estate and vehicles; the IT contracts and equipment service agreements entered into after the transition date were not scanned. The remediation is a contract-by-contract review of every service agreement over a defined threshold executed in the post-transition years, with the embedded-lease analysis documented and any identified leases added to the subledger with the appropriate prior-period adjustment under ASC 250 (which is typically immaterial in mid-market when caught in the second or third year, but compounds quickly). Stale discount rates. The discount rate selected at transition was not re-evaluated for new leases entered into in subsequent years. New leases at higher market rates were recorded at the transition rate, understating the lease liability. The remediation is to re-derive the incremental borrowing rate for each lease commencement date in the post-transition years and re-measure the affected leases. The cumulative adjustment is sometimes material; the going-forward fix is to document the IBR-derivation procedure and run it for every new lease. Modification accounting errors. Modifications were processed as if they were new leases, or were ignored entirely, with the underlying lease continuing on its original schedule. The auditor finds these by walking the modification log against the contract files. The remediation is to re-analyze every modification in the period under review, recalculate the affected leases, and post catch-up entries. ROU rollforward that does not tie to GL. The lease subledger total at period-end does not match the GL ROU asset balance, with the difference unexplained. The cause is usually a mix of journal-entry posting errors, leases that were modified in the subledger but not in the GL, and prior-period adjustments that affected one ledger but not the other. The remediation is a full reconciliation between the subledger and the GL with every variance investigated and resolved. Disclosure errors. The maturity analysis in the footnote does not tie to the subledger; the weighted-average remaining lease term and discount rate are calculated incorrectly; the components of lease cost are misclassified. The disclosure errors are often the first thing the auditor flags because the footnote is the most public artifact of the implementation. The remediation is to rebuild the disclosure from the subledger using the disclosure module of whichever software the firm uses, with the controller verifying every line. What we recommend ASC 842 is not a project that ends. The implementations that survive the audit treat the standard as an operational practice with five recurring procedures. Run the embedded-lease scan on every new contract over a defined dollar threshold as part of the contract-execution workflow. The scan is a documented procedure with a sign-off; the output is either a new lease added to the subledger or a documented determination that the contract does not contain a lease. The threshold should be set low enough to catch material embedded leases, typically twenty-five thousand dollars in annual contractual commitment for IT and equipment, lower for industries with concentrated supplier relationships. Maintain the lease subledger in a dedicated tool (LeaseQuery, Visual Lease, or NetLease for NetSuite shops) for any portfolio over fifteen leases or with embedded-lease complexity. The tool generates the journal entries, the rollforward, and the disclosure. The controller verifies the inputs, not the calculations. Re-derive the discount rate at each lease commencement and at each modification triggering remeasurement. Document the IBR derivation in a memo for each commencement: the firm's borrowing rate at the date, the term-matched adjustment, the collateral and security adjustment if applicable, and the supporting market data. The memo is filed in the lease file. For private companies electing the risk-free-rate practical expedient, document the asset-class election and the rate source (typically a Treasury rate from FRED). Run a quarterly lease subledger review with the controller, the lease accountant (or designee), and the FP&A lead. The review walks the modification log, verifies that every modification has been correctly processed, ties the subledger total to the GL, and reviews the next-quarter activity (commencements, modifications, terminations). The review is documented and reviewed by the audit committee. Build the annual policy refresh as part of the year-end close. The lease policy, discount rate methodology, practical-expedient elections, embedded-lease scan threshold, modification procedures, is reviewed by the controller and CFO, signed, and filed. Any changes from the prior year are documented and disclosed if material. The implementation checklist included as the artifact for this guide is the version we run when a firm engages us to clean up a drifted implementation. It is sequenced, embedded-lease scan first, then abstraction verification, then calculation rebuild, then rollforward and disclosure, because that is the order in which the foundation has to be rebuilt before the calculations on top of it can be trusted. Cross-link to the accrual discipline guide for the broader cutoff procedures that the lease accounting fits inside, and to the 10-day close calendar for where the lease procedures land in the operational rhythm.