Extract lease terms from the agreement, propose the classification and discount rate, build the right-of-use and liability schedules, maintain the asset register, and flag remeasurement triggers, with every posting accepted by the financial controller.
A lease or service agreement arrives from the contract repository, ERP or lease-accounting system.
02
A term, payment schedule and option set are normalised, each figure keeping the clause it came from.
Reason
03
An agreement is screened for an identified asset and a right to control its use, surfacing embedded-lease candidates.
04
A classification test and a proposed discount-rate input are drafted against the configured rate hierarchy.
05
A right-of-use and liability schedule is built, and the fixed-asset register carries placed-in-service dates forward.
Decide
06
A renewal, option exercise or contingency resolution is checked against the modification-versus-remeasurement rule.
07
An embedded-lease candidate, a classification or a rate proposal is routed to the named lease accountant for review.
Out
08
A clause, a schedule, its flags and the accountant's disposition are retained against the lease and the register.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent proposes the classification and the rate input; the financial controller decides, posts every entry, and the company stays the preparer of record.
Example workflow
One lease, agreement to posting
AgentHuman
1Agreement receivedLease agreement, amendment, contract repository entry or ERP record
2Terms assembledPayment schedule, options, embedded-lease candidates and prior schedule, each with its clause
3Schedule proposedClassification, rate input, schedule and confidence
4Controls appliedIdentified-asset check, classification-test check, remeasurement gate and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing posts at any of them — the agent is drafting the schedule, and the accountant's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the lease accountant to approve.
Low confidence
Adds a senior-accountant read first.
Controller approval
The schedule is held with its source clauses, its flagged triggers and the confidence.
Approve · Edit · Send to senior review
Approved — ready to post▼
6Asset register updatedOnly where write access and approval policy allow it
7Outcome evaluatedClassification correctness, remeasurement outcomes, controller edits and post-posting corrections
Edits
Every controller edit is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Concluding that a contract contains a lease.
Setting the discount rate.
Classifying a lease as finance or operating.
Recording an impairment.
Automation boundaryAgent acts unaided
✓Extract lease terms and flag embedded-lease candidates for review.
✓Apply the configured classification tests and the rate hierarchy.
✓Build the schedules, and roll the fixed-asset register forward.
✓Flag remeasurement triggers and hold the schedule.
Any write happens inside the boundaries agreed at implementation, never ahead of approval.
Deciding a useful life or a placed-in-service date.
Confirming a common-control related-party relationship.
Electing a short-term or low-value class exemption.
Posting an entry to the register or the ledger.
Example output
One schedule line, annotated
Everything the agent builds is attached to the clause it was drawn from.
Lease-schedule output · single leaseIllustrative example
Lease
Schedule line
Liability (PV)
Source clause
Confidence
Preparer of record
Distribution-center lease
Ten-year term with two five-year renewal options, proposed at the incremental borrowing rate
$1,240,000
Lease agreement, Section 4
89%
Lease accountant name and title
As receivedTaken from the lease agreement and the prior schedule — nothing on this side is a conclusion the agent reached.
An overall extraction-accuracy score can look strong while errors concentrate in one asset class. Nestack reports the schedule-rework rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Service contracts with embedded leases
7.6%
4.0×
Review
Leases with renewal and purchase options
5.0%
2.6×
Review
Variable-payment and index-linked leases
3.2%
1.7×
Watch
Fixed-payment real-estate leases
1.9%
0.8×
Normal
Bar: schedule-rework rate lift vs. the fixed-payment real-estate baseline · scale 0–4.0× · tick at 2.0×2 of 4 slices over threshold
Evidence-linked improvement
The loop closes when the schedule is retested, not explained
A cycle ends when the wrong remeasurement is a case the next release has to pass. That suite is what the next schedule built is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Schedule-rework rate rises in an asset-class slice.
02Diagnose
The schedule that quietly reset traces back through its clauses until the cause narrows to one.
03Improve
Version-stamp the correction and attach the schedules that exposed it.
04Verify
The affected cases run again, and a fail stops the release.
05Learn
It becomes a permanent test, and the classification rules move with it.
Learn → DetectThe return edge. The next schedule built is checked against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, schedule-drafting workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Lease-workflow discovery and the automation boundary.
02Lease-system and document-source review.
03Classification-test and rate-hierarchy policy mapping.
04Lease-term ingestion and normalisation.
05Drafting logic and lease detection.
06Confidence scoring and flag routing.
07Controller approval workflow.
08Register and ERP integration.
09Remeasurement and classification cases.
10Guardrails and posting controls.
11Schedule-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne lease, one officeProductionProduction register integrationAdvancedMultiple entities / portfolios
Introduced at Pilot
Drafting to your terms and rules✓✓✓
Controller approval✓✓✓
Extraction-accuracy baseline✓✓✓
Introduced at Production
Reporting by asset class—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Asset-register integration—✓✓
Introduced at Advanced
Multi-standard lease rules——✓
Multi-stage controller approvals——✓
High lease volume——✓
Multi-standard lease controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, lease volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your lease agreements and prior schedules→Lease-record ingestion and clause mappingWeek 1
02Representative executed leases and amendments→Term ingestion and normalisation, and the schedule baselineWeek 2
03Your classification policy and rate-hierarchy elections→Classification-test and rate-hierarchy mappingWeek 1
04Access to relevant APIs, feeds or exports→Lease-system and document-source assessment, then integration setupWeek 2
05Schedules you would not want posted→Embedded-lease cases and the evaluation suiteWeek 4
06What no schedule may infer→Confidence scoring, flag routing, guardrails and posting controlsWeek 3
07Named lease accountants to review schedules→Controller approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bands follow the work as it actually falls, so week 5 holds evaluation and pilot at once.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Lease workflow discovery, classification mapping and the automation boundaryW2Source integration and the schedule-drafting baselineW3Drafting workflow, confidence logic and approval controlsW4Classification, remeasurement and impairment case testingW5Register integration, pilot leases and targeted correctionsW6One close cycle posted under the financial controller, then Agent Care handover
Reading the bandA band covers the weeks its work is named in, and no others. The week 5 overlap is real, not padding.
At the end of W6Once the cycle validates, monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Accounting AI agent
Build a lease and fixed-asset agent around your controller's approval chain.
Show us your lease agreements, your classification policy and who signs off. You get terms extracted, a schedule built against a rate you approve, and a register your controller can post from.
