Is the dedicated lease accounting tool still worth renewing if the ERP can run ASC 842 itself? For a mid-market portfolio of a few hundred real-property and equipment leases, probably not: an agentic ERP that extracts, classifies, schedules, remeasures and posts against one ledger absorbs the subledger work without the integration tax.
The answer flips when the portfolio looks less like office space and more like rolling stock. Lessor accounting, high-volume equipment fleets and industries where the lease is the operating asset still reward a dedicated subledger. The deciding factor is rarely the arithmetic of ROU assets; it is whether the controller can tie the schedule to the general ledger daily without re-keying.
Why the Lease Bolt-On Category Exists
The subledger market was sized to a specific problem: off-balance-sheet lease commitments. In 2005 the SEC's Sarbanes-Oxley report to Congress estimated that publicly traded companies kept approximately $1.25 trillion in off-balance-sheet lease commitments, which eventually produced ASC 842 and IFRS 16. When those standards arrived, legacy ERPs could not handle variable payments, embedded options, incremental borrowing rate schedules or the asymmetric treatment of finance versus operating leases without heavy customization.
Pre-adoption surveys captured the response. A PwC and CBRE study found 43% of respondents planned a new lease management system while another 20% planned to modify the existing ERP. That split funded LeaseQuery, Visual Lease, LeaseAccelerator, Nakisa and CoStar's subledger products. Monthly batch postings into NetSuite or SAP became the default architecture, and finance inherited an extra reconciliation point between the subledger and the ledger.
Two things have shifted. Controllers now know what the subledger duplicates and what it genuinely owns. And the ERP tier has changed: an agentic platform like the erp.io platform can execute the lease workflow against the ledger directly, which is a different question from "can we bolt a schedule generator onto NetSuite."
The Five Steps an ERP Has to Run End to End
Running ASC 842 inside the ERP means doing the same five things a bolt-on does, in order, without stepping outside the ledger's boundary of truth:
- Extract. Parse the executed lease for parties, commencement and end dates, base rent, escalations, renewal and termination options, residual value guarantees, variable payments and any embedded service component.
- Classify. Finance or operating, applying the ASC 842-10-25-2 tests against the terms and the incremental borrowing rate at commencement.
- Schedule. Build the right-of-use asset and lease liability amortization, straight-lined for operating leases and front-loaded for finance leases, with the IBR, discount factors and expected cash flows exposed for review.
- Remeasure. On modification, index or rate reset, option reassessment or impairment, rebuild the schedule from the remeasurement date and post the delta to the correct period.
- Post. Write journal entries to the ledger with full traceability from each line back to the underlying lease document and remeasurement event.
In an agentic ERP, agents handle the first four steps and the deterministic ledger owns the fifth. The AI never writes to the ledger directly; every entry traces back to an approved schedule that can be reproduced from the source document. The split mirrors the broader pattern described in AI-native ERP architecture: orchestration and extraction above the line, immutable postings below it. It is the same discipline applied to ASC 606 for usage-based revenue, where the agent proposes and the ledger records.

Where a Dedicated Lease Subledger Still Earns Its Keep
The agentic-ERP case thins out once the portfolio stops looking like real estate and starts looking like inventory. Three situations keep a dedicated subledger worth its cost.
Lessor accounting under ASC 842 is the clearest. Sales-type and direct-financing leases, interest income recognition, and the reporting required of a company whose business model is to lease assets, not to sign a few office leases, remain thin ground inside generalized ERPs. Equipment-heavy portfolios are the second: a fleet of ten thousand forklifts, MRI machines or trailers with return logistics, maintenance schedules and residual value forecasts needs an operational layer the ledger does not provide. The third is sector exposure. An EY study of 58 Fortune Global 500 companies found that balance-sheet impact varied by an order of magnitude across industries, and the industries that moved most are the ones where lease arithmetic becomes a core operating metric.
If the company sits in one of the top-impact bands, the controller is not just closing the books; they are managing a lease portfolio as an asset class. The dedicated tool earns its integration tax there. For a professional services firm with eighteen office leases and a handful of copiers, it does not.
ROU Asset Reconciliation and the Material-Weakness Risk
The specific failure mode controllers should be designing against is the missed remeasurement. A lease amendment is signed, it reaches accounting weeks late, the schedule is never rebuilt, and the ROU asset carries a balance that no longer reconciles to the underlying obligation. In 2026 Where Food Comes From filed a 10-K/A disclosing a material weakness after a November 2025 lease amendment produced a material overstatement of right-of-use assets and other income for fiscal year 2025. The amendment was real; the remeasurement was not, and the auditors caught it.
The SEC pattern around these failures is well documented. A Deloitte review of staff comment letters shows ASC 842 comment threads resolving in 35.39 days on average, with repeat questions around disaggregation of lease cost, IBR methodology and maturity analyses that fail to tie to the balance-sheet lease liability. A bolt-on tool does not prevent any of these; it moves the reconciliation to a different system.
The architectural answer is daily reconciliation of the ROU asset and lease liability to the ledger, run by an agent that can detect a modification before the auditor does. The subledger-to-ledger tie becomes trivial when the schedule lives in the same database as the posting.
What Settles the Renewal Decision in Practice
Four tests separate a portfolio that still wants a dedicated subledger from one that is paying for a solved problem. Count the modifications: fewer than thirty remeasurement events a year means a subledger optimized for modification volume is under-used. Look at the integration surface: if the bolt-on exchanges files monthly and someone re-keys adjustments at close, the "integration" is a manual reconciliation. Audit the last three ROU reconciliations: small differences that took half a day to chase point at the architecture, not the tool. And price the renewal against the categories where AI agents still miss: lessor-side interest recognition, non-standard document layouts and jurisdictions with local lease filings are where a dedicated tool keeps an edge.
Controllers running a mid-market real-estate-heavy portfolio should plan to execute ASC 842 inside the ERP and let the bolt-on contract lapse at renewal; the integration tax outweighs the schedule engine. Teams with lessor accounting, equipment fleets at scale or exposure to the industries EY identified as most impacted should keep the dedicated subledger and focus the ERP project on daily reconciliation of the schedule to the ledger. If the position is unclear, pressure-test it against a real amendment rather than a vendor demo; a short free assessment against the actual lease portfolio tends to settle it faster than another RFP cycle.
