All products
Audit & Assurance
CA Audit
AboutContactSupportSign InBook a Demo →
IFRS 16 · Ind AS 116 · Lessee and lessor

Both sides of the lease. One sub-ledger.

Lessees got one model under IFRS 16; lessors kept two, and the two share almost no measurement logic. Most tools pick a side. FinIFRS runs both: a lessee engine for right-of-use assets and lease liabilities, and a lessor engine that branches at classification into finance and operating — each feeding a balanced journal, a disclosure pack and a hash-chained audit trail. Contracts come in through a form, an Excel importer or AI extraction, and all three call the same engine.

✓ Lessee: ROU + liability✓ Lessor: finance and operating✓ ¶44–46 modification decision tree✓ CPI and index-linked resets✓ AI contract extraction with review✓ Three doors, one engine
2
Engines — lessee and lessor — feeding one sub-ledger and one disclosure pack
7
Gates every lessor lease passes: lease? components, enforceable period, term, payments, classification, events
3
Ways in — form, bulk Excel, AI extraction — all calling the same engine
37
Lessor tables with row-level security forced on every one
The problem

A lease register in Excel is a model nobody audits.

Discount rates typed once and never revisited, modifications booked as new leases, CPI resets applied by overwriting the schedule, and a lessor book that treats every lease as operating because the classification test was never run.

Modifications

¶44–46 decide whether a change is a separate lease or a remeasurement, and at which rate. Overwriting the schedule loses the gain or loss and the history.

The lapsed expedient

The ¶46A rent-concession relief only covered payments due on or before 30 June 2022. A concession granted now must be remeasured — many registers still credit it to P&L.

Lessor classification

Finance or operating is decided at inception, not commencement, and drives everything after. Spreadsheets rarely store which date the test used.

What others can't do

What a single-sided lease tool cannot do.

Real estate groups, equipment lessors and NBFCs that both lease in and lease out need both engines — and need them to agree.

ONLY HERE · 01

Both sides, one platform

Right-of-use leases in and finance or operating leases out, with intercompany pairs visible from both ends.

ONLY HERE · 02

Modifications as a decision tree

Scope increase, scope decrease, term change and consideration change routed through ¶44–46 with the revised rate and the P&L delta — history preserved.

ONLY HERE · 03

The rule lives in the engine

The ¶46A sunset is enforced in the engine, so the form, the API, the CPI batch and any future import are held to the same rule.

ONLY HERE · 04

Lessor done properly

Inception vs commencement kept apart, IRIL solved, net investment unwound, straight-line operating income, ECL on lease receivables and residual value review.

ONLY HERE · 05

Index resets in batch

Load a CPI index once; every linked lease is remeasured through the same event engine.

ONLY HERE · 06

Three doors, one room

Form, Excel and AI extraction all call one create function. A bulk-loaded book produces the same figures to the rupee as a hand-typed one — and a test proves it.

What is inside

What is inside.

Two engines, one governance layer.

L-SCHLessee schedulesLease liability at the incremental borrowing rate, ROU asset, depreciation and interest, with escalations.
L-EVTLessee eventsSix validated event types through the ¶44–46 modification tree; remeasurement from the effective period.
L-IDXIndex & CPI resetsIndex tables and batch remeasurement of every linked lease.
L-RESRestoration & depositsRestoration provisions and security deposits at present value with their unwind.
L-EXPExpiry & tasksExpiry pipeline, option decisions and review tasks before a lease rolls off.
L-DUPDuplicate detectionThe same lease uploaded twice is caught before it doubles the liability.
R-CLSLessor classificationFinance vs operating at inception against the ¶63 indicators, stored with its evidence.
R-FINFinance lease engineIRIL, net investment, finance income and receivable unwind.
R-OPSOperating lease engineStraight-line income, incentives, underlying-asset depreciation.
R-ECLLease receivable ECLSimplified-approach impairment on finance and operating receivables.
JNLJournalsBalanced vouchers per period under four-eyes review.
DISDisclosuresMaturity analyses, movement schedules and the lessee / lessor notes.
LIBDocument libraryContracts scanned, stored and served only once they scan clean.
AUDAuditHash-chained trail of every create, event and approval.
AI-native · 3 live

AI reads the contract. The engine does the accounting.

Lease onboarding is document work. That is where the model is used — with confidence, provenance and a second review.

Lessee contract extraction

Live

PDF or Word contracts read into a draft lease — parties, dates, payments, escalations, options — with a verify pass before a person commits it.

Lessor contract extraction

Live

The same pattern on the lessor side, routed to a review queue with field-level confidence and provenance.

Lease copilot

Live

Ask about a lease or the book; answers come from the stored schedule and events through lease-specific tools.

Option-exercise likelihood

Roadmap

Signals on renewal and termination options to support the ‘reasonably certain’ judgement — as evidence, never as the decision.

The boundary

Across every FinIFRS product the rule is the same: a deterministic, tested engine computes and stores every figure first. AI reads documents, drafts sentences and answers questions over what is already stored — it never computes, posts or approves an amount.

Highly configurable

Policy as configuration.

The judgements that differ by entity are settings with an approval, not code.

Incremental borrowing rate curves by currency, tenor and entity.
Low-value and short-term exemptions and their thresholds.
Component separation policy by asset class.
Depreciation method for ROU and underlying assets.
Index tables and reset frequencies.
Reporting periods, closing calendars and GL mappings for every posting.
Neck and neck

Side by side.

Against the lease tools and registers finance teams use today.

CapabilityLessee-only lease toolExcel registerFinIFRS
Lessee and lessor on one platformLessee onlyTwo workbooks✓ Both
¶44–46 modification decision treePartialOverwrite✓ With history
¶46A sunset enforced——✓ In the engine
Lessor inception-date classification—Rarely✓ Stored with evidence
CPI batch remeasurementManualManual✓ One upload
AI contract extraction with reviewSome—✓ Both sides
Same figures from form, bulk and AI——✓ One engine, tested
The questions the room actually asks

We only lease in. Is this overkill?

Licence the lessee side alone — the lessor engine is a separate grant. You can add it later without re-loading anything.

How do you treat a rent concession granted today?

As an ordinary lease modification under ¶44–45. The ¶46A expedient lapsed for payments due after 30 June 2022, and the engine enforces that for every entry route.

Can we trust AI-extracted leases?

Extraction produces a draft with field-level confidence and provenance; low-confidence fields route to a second review. Nothing reaches the ledger until a person commits it through the same engine as a hand-typed lease.

The low-risk way in

Send us twenty contracts. Get back a reconciled register.

We extract, measure and reconcile a sample of your leases — both sides if you have both — and show you the modification and classification findings in your current register.

Works with
Beyond the product lines

We build the AI-native finance automation you can't buy.

A regulator's bespoke return, a partner settlement, a reconciliation between two systems only you run. We build it to your requirement on the same engines, audit trail and AI boundary our products run on — in weeks, with golden tests, and handed over as configuration your team owns.

01Deterministic where money movesEvery figure is computed by a tested engine — never by a model.
02AI where documents and questions areExtraction, narrative and Q&A over stored facts, with validation.
03Governance from day oneHash-chained audit, maker-checker and tenant isolation, inherited.
04Yours to changeRules as versioned configuration your controllers edit after go-live.