AI Lease Accounting Software for ASC 842 and IFRS 16: 2026 Evaluation Guide

If your team manages lease portfolios under ASC 842 or IFRS 16, you already know the calculation is not the hard part. The hard part is keeping the data complete, capturing every modification and renewal, and producing disclosures that survive auditor scrutiny. AI lease accounting tools promise to fix all of that. Most of them fix only some of it.

This guide gives controllers, lease accounting managers, and CFOs a vendor-neutral framework for evaluating AI lease accounting software: what the tools actually automate, where errors still originate, what auditors expect when AI generates journal entries, and how to structure a pilot before committing.

Key takeaway: Most lease accounting errors originate upstream of the calculation engine, in incomplete lease data and uncaptured modifications. The tools that add the most value are the ones that fix that data layer, not just the arithmetic.

Why Lease Accounting Is Still Hard in 2026

ASC 842 and IFRS 16 are not one-time setup exercises. Both standards require lessees to recognise most leases on the balance sheet as a right-of-use (ROU) asset and a corresponding lease liability, then account for them continuously through modifications, reassessments, renewals, and terminations.

ASC 842 became effective for US public companies for fiscal years beginning after December 15, 2018, and for private companies for fiscal years beginning after December 15, 2021. IFRS 16 replaced IAS 17 for annual reporting periods beginning on or after January 1, 2019. Both standards have since been amended: FASB has issued multiple codification improvements under Topic 842, and the IASB's 2023 amendment on "Lease Liability in a Sale and Leaseback" took effect for periods beginning on or after January 1, 2024. Any AI tool you evaluate must incorporate that 2023 amendment.

Approximately 58% of public companies found ASC 842 implementation more complex than anticipated, and the ongoing accounting proved harder than the initial setup. A lease portfolio spanning real estate, equipment, vehicles, and embedded leases generates accounting events every period. Each modification, renewal, or termination changes the ROU asset and lease liability and requires recalculation under specific accounting treatment rules. That volume of events, across potentially thousands of leases, is where manual processes break down.

The Two-Layer Framework: Engine vs. Data Layer

Understanding this distinction is the most useful thing you can do before evaluating any AI lease accounting tool.

The market has two distinct layers, and most vendor pitches conflate them:

As Kognitos summarises: "The engine calculates correctly on the data it has; if the lease population is incomplete, the data is scattered and outdated, or modifications and reassessments are not captured and processed correctly, the accounting is wrong regardless of how good the engine is."

Most lease accounting errors originate in the second layer, not in the calculation engine. Evaluating tools without this framework leads teams to buy a better calculator when what they need is a better data pipeline.

The Lease Accounting Engine

The major lease accounting engines, including LeaseQuery/FinQuery, Visual Lease, Nakisa, LeaseAccelerator, NetSuite Lease Accounting, SAP, and Trullion, automate the core ASC 842 and IFRS 16 mechanics:

• Lease classification (operating vs. finance under ASC 842; single finance-lease-style model under IFRS 16)
• Initial measurement of the ROU asset and lease liability at present value
• Amortisation schedules and period-by-period journal entries
• Required disclosures: maturity analyses, weighted-average rate and term tables

Note the classification difference: IFRS 16 does not distinguish between operating and finance leases for lessees, while ASC 842 does. This creates a systematic difference in P&L presentation between IFRS and US GAAP reporters, and AI tools must handle both classification logics correctly for multinational entities running parallel books.

The Upstream Data and Events Layer

This is where AI adds the most incremental value and where most implementations either succeed or fail. The capabilities to look for:

Lease abstraction. AI reads unstructured lease contracts (often long PDFs) and extracts the terms relevant to accounting: payment amounts and schedules, commencement and end dates, renewal and termination options, discount-rate inputs. Tools like Trullion use OCR and NLP to extract this data and maintain traceability back to the source clause, so auditors can verify what the system read and where it found it.

Embedded lease detection. Leases hidden inside service or supply contracts are one of the most common ASC 842 compliance failures. IT contracts, logistics agreements, and real estate arrangements frequently contain embedded leases that manual review misses. AI can scan supplier agreements for embedded lease indicators, flagging contracts for human review. The SEC has specifically flagged embedded lease completeness as a recurring comment letter focus.

Modification and event handling. Modifications, reassessments, renewals, and terminations are the most error-prone area of ongoing lease accounting. AI helps process these events by applying the correct accounting treatment and recalculating the ROU asset and liability. This is also where misclassification risk is highest: if AI applies the wrong event type, the resulting entries are wrong in a way that compounds over subsequent periods.

Exception flagging and reconciliation. AI can compare extracted contract data against the lease register, flag gaps or duplicate records, and alert finance teams to potential remeasurements before month-end close.

ASC 842 vs. IFRS 16: What Differs in AI Tool Requirements

Multinational companies often run both standards simultaneously, with US subsidiaries reporting under ASC 842 and international subsidiaries under IFRS 16. AI tools must handle both, but the requirements differ in ways that matter for tool selection:

For the IASB's 2023 sale-and-leaseback amendment specifically: it changed how sellers-lessees measure lease liabilities in sale-and-leaseback transactions. Any IFRS 16 tool you evaluate must confirm it has incorporated this change for periods beginning on or after January 1, 2024. Ask vendors directly; do not assume.

For US GAAP, FASB has issued a series of amendments since ASU 2016-02, including ASU 2018-11 (transition practical expedients) and ASU 2021-05 (lessors and variable lease payments). Confirm your tool reflects the full amendment stack.

What Auditors Expect When AI Generates Lease Entries

External auditors are increasingly scrutinising AI-generated outputs, and the bar for traceability is higher than many finance teams expect.

For any AI-generated journal entry or disclosure to be auditable, reviewers must be able to see:

1. What the AI extracted from the source document
2. Which clause or page supported that extraction
3. Whether a qualified person reviewed and approved the output
4. The full audit trail from source contract to posted entry

As House of Control notes: "For audit purposes, reviewers should be able to see what the AI extracted, where it found the information and whether the result was approved or corrected."

Tools like Trullion generate 100% auditable journal entries with source data traceable back to the original contract. This is the standard to hold all vendors to, not a premium feature.

The SEC's comment letter programme has specifically flagged three recurring ASC 842 issues that AI tools can help address:

• Completeness of the lease population, including embedded leases
• Adequacy of discount rate disclosures
• Appropriateness of lease term determinations, including renewal option assessments

AI that improves data completeness and audit trails directly addresses these SEC staff concerns. But AI that generates entries without a clear human approval step creates a new control gap that auditors will find.

The Governance-First Principle

Do not deploy AI on a broken process. This is the dominant expert consensus, and it is worth stating plainly before any tool evaluation.

Karl Oscar Rosli, Lease Accounting Expert at House of Control, puts it directly: "AI can help finance teams move faster, but it cannot compensate for unclear ownership, weak lease data or missing evidence. The teams that will benefit most from AI are the ones that first build a controlled IFRS 16 process."

If your lease register has duplicates, gaps, or data stored across local spreadsheets, AI will process that poor data faster. The output will be wrong at scale instead of wrong manually.

The OECD AI Principles on trustworthy AI, transparency, robustness, and accountability translate into four practical controls for lease accounting:

• Human oversight on all material accounting judgements
• Documented evidence linking AI outputs to source documents
• Clear approval rights for judgement-based inputs
• Ongoing monitoring of AI exceptions and error rates

What Must Stay Human-Reviewed

These IFRS 16 and ASC 842 areas involve judgement or material impact and should not be fully automated without explicit rules, review, and sign-off:

• Lease term assessments, including renewal option probability
• Incremental borrowing rate (IBR) determination and discount rate methodology
• Modification treatment (whether a modification is a separate lease or a change to an existing one)
• Impairment indicators on ROU assets
• Journal postings for material amounts

AI can prepare suggestions and flag exceptions in each of these areas. Finance, treasury, or group reporting must own the final decision.

How to Evaluate AI Lease Accounting Tools: A Six-Criterion Framework

When comparing platforms (Trullion, LeaseQuery/FinQuery, Visual Lease, Nakisa, LeaseAccelerator, NetSuite, SAP, or agentic platforms like Kognitos), assess each against these criteria:

1. Abstraction Accuracy and Traceability

Ask vendors for their extracted-field accuracy rate on a sample of your own contracts. Acceptable accuracy depends on your portfolio complexity, but you need a re-abstraction workflow for when AI makes mistakes. The tool must show which clause supported each extracted value, not just the extracted value itself.

Good questions to ask:

• What happens when the AI is uncertain? Does it flag confidence scores or route to a review queue?
• Can it handle amendments and associate them with the original lease?
• How does it handle handwritten or scanned legacy contracts?

2. Amendment and Standards Currency

Confirm the tool has incorporated:

• The full FASB ASU stack for ASC 842 (through ASU 2021-05 at minimum)
• The IASB's 2023 sale-and-leaseback amendment (effective January 1, 2024) for IFRS 16
• FRS 102 Section 20 if you have UK entities (effective for periods beginning January 1, 2026)

Ask for the vendor's standards update policy and how quickly amendments are reflected in the calculation engine.

3. Modification and Event Handling

This is where most errors occur. Test the tool against your most common modification scenarios: partial terminations, lease extensions, rent concessions, and index-linked payment changes. The tool should apply the correct accounting treatment for each event type and recalculate the ROU asset and liability automatically, with a clear audit trail.

4. Audit Trail Quality

Every extracted field, every calculation, every journal entry, and every approval must be timestamped and attributable. The audit trail must run from source contract to posted entry without gaps. This is not optional for audited financial reporting.

5. ERP Integration

For large enterprises, the critical implementation question is whether the AI layer sits inside or outside your ERP. NetSuite-native solutions like NetLease post directly to the general ledger without third-party integration. SAP and Oracle users typically need a dedicated lease accounting module or a certified integration. Standalone platforms like Trullion and Visual Lease connect via API. Confirm the integration is bidirectional: lease events should flow from the AI tool into the ERP, and payment data should flow back.

6. Data Security and Confidentiality

Lease contracts contain commercially sensitive terms: rent amounts, renewal options, break clauses, and counterparty details. Before uploading contracts to any AI platform, confirm:

• SOC 1 Type 2 and SOC 2 compliance
• Data residency and retention policies
• Whether contract data is used to train the vendor's models
• Access controls and role-based permissions

This question will come from your legal, procurement, and IT security teams. Have the answers before the implementation conversation.

A Practical AI Readiness Roadmap

Before deploying AI in your lease accounting workflow, work through these five steps in order:

1. Assess lease data completeness. Identify gaps, duplicates, and leases stored outside the central register. This includes embedded leases in service and IT contracts.
2. Standardise key fields. Agree on the data fields required for calculations and disclosures, and enforce consistent formats across the portfolio.
3. Define ownership. Specify who reviews and approves each category of judgement-based input: lease term, IBR, modification treatment.
4. Build the audit trail. Every material change must be timestamped, attributable, and linked back to the source contract, calculation, and approval before AI enters the workflow.
5. Pilot on one narrow use case. Good first pilots include extracting payment clauses from new contracts, checking for missing lease data in one entity, or running cross-period consistency checks on disclosures.

Measure the pilot against concrete metrics: extracted-field accuracy rate, exception rate, approval time, rework volume, and audit findings. These numbers tell you whether to scale.

The safest deployment model is assistive AI: the system proposes, finance reviews, and an accountable person approves. Full automation without human review is not appropriate for material accounting judgements under either standard.

For broader context on AI governance controls in finance workflows, see Finrep's AI financial close automation guide and the AI contract review evaluation framework, which covers the upstream contract ingestion layer in more depth.

FAQ

Is ASC 842 still relevant in 2026? Yes. ASC 842 has been the operative US GAAP lease accounting standard since 2019 for public companies and 2022 for private companies. It is not being replaced or significantly revised. The ongoing compliance burden, particularly around modifications, reassessments, and embedded lease identification, is what drives demand for AI automation.

Is IFRS 16 the same as ASC 842? The core model is similar: both require lessees to recognise an ROU asset and lease liability for most leases. The key difference is that IFRS 16 uses a single lessee accounting model (all leases treated like finance leases), while ASC 842 distinguishes between operating and finance leases with different P&L presentation. This means AI tools must handle different classification logic for IFRS and US GAAP reporters. The IASB's 2023 sale-and-leaseback amendment, effective January 1, 2024, is also a live compliance difference that ASC 842 does not mirror.

What is the 90% rule in lease accounting? The 90% threshold is a bright-line test from the predecessor standard ASC 840, where a lease was classified as a capital lease if the present value of minimum lease payments equalled or exceeded 90% of the asset's fair value. ASC 842 replaced this with a principles-based test: a lease is a finance lease if the present value of lease payments is substantially all of the fair value of the underlying asset. FASB did not define "substantially all" in ASC 842, but many practitioners continue to use 90% as a practical benchmark. AI tools should apply the principles-based test, not a hard-coded 90% rule.

Can AI handle lease modifications automatically? AI can apply the correct accounting treatment and recalculate the ROU asset and liability when a modification is captured. The risk is misclassification: whether a modification is a separate new lease or a change to an existing lease requires judgement, and AI can get this wrong. Modifications should be reviewed and approved by a qualified accountant before entries are posted.

What governance controls do auditors expect when AI is used in lease accounting? Auditors expect a complete audit trail from source contract to posted entry, evidence of human review and approval for material judgements, and the ability to see what the AI extracted and where it found the information. Tools that generate entries without a documented approval step create a control gap. The OECD AI Principles on transparency and accountability are the applicable governance framework.

Should we buy a dedicated lease accounting platform or use our ERP module? ERP-native modules (SAP, NetSuite) reduce integration complexity and keep lease data inside your existing system of record. Dedicated platforms (Trullion, Visual Lease, LeaseQuery/FinQuery) typically offer deeper AI abstraction capabilities and more granular audit trails. The right answer depends on portfolio complexity, ERP maturity, and whether your primary pain point is the calculation engine or the upstream data layer. For large, dynamic portfolios with frequent modifications, a dedicated platform with strong AI abstraction usually delivers more value than an ERP module alone.