What is an embedded lease?

A lease contained within a contract that is not called a lease. Under ASC 842 it exists where the contract conveys the right to control the use of an identified asset for a period in exchange for consideration. Service, supply and IT agreements are common sources.

Does it replace reading the contract?

No, and it should not. It extracts the accounting-relevant provisions, shows where each one appears, and produces a cited analysis — so the reading you do is targeted rather than exhaustive.

Can it handle a portfolio of similar contracts?

Yes, and that is where consistency matters most. The same framework applied across a class of contracts is what keeps two similar arrangements from being concluded differently.

What about contracts our legal team has already reviewed?

Legal review and accounting review look for different things. A contract can be legally sound and still contain an embedded lease nobody accounted for.

Contract Analysis for Accounting Teams | Revenue, Lease & Embedded Terms

This is not legal contract review. Legal teams have good tools for redlining, obligations tracking and risk language. What those tools do not do is tell you that clause 7.3 creates a material right, or that the equipment provision buried in a services agreement is an embedded lease.

Two different jobs, often confused

Capability	Legal contract review	Accounting contract review
Question being asked	What are we obligated to, and where is our risk?	What does this contract require us to recognize, and when?
Looking for	Indemnities, liability caps, termination rights, IP	Performance obligations, variable consideration, embedded leases, material rights
Output	Redlines, a risk summary, a negotiation position	An accounting conclusion, cited, with a memo behind it
Reviewed by	Counsel	A technical accountant, then an auditor

Both matter. They are not substitutes, and a tool built for one does not do the other. Gaapio is built for the second.

What accounting teams are actually looking for

Embedded leases

Service, supply, logistics and IT agreements that convey the right to control an identified asset. Nothing in the title says lease. The ASC 842 criteria still apply.

Revenue terms that change the answer

Material rights, options at a discount, acceptance provisions, termination rights, and variable elements that need estimating and constraining.

Debt agreements and guarantees

Credit agreements and other financing documents carry their own accounting consequences — embedded derivatives requiring bifurcation analysis under ASC 815, and guarantees under ASC 460. Different standards, same problem: the answer is in the document.

The clause nobody flagged

The one negotiated late, agreed by someone outside finance, that shifts a conclusion — and surfaces during the audit rather than during the close.

How it works

1
Upload the contract and its attachments. Master agreement, order forms, side letters, amendments. The accounting answer frequently lives in the attachments.
2
Extract the accounting-relevant terms. Not a summary of the document — the specific provisions that drive recognition, measurement and classification, each linked back to where it appears.
3
Run the standard-specific analysis. ASC 606 for revenue arrangements, ASC 842 for anything that might contain a lease, with the reasoning written out.
4
Flag what is non-standard. Provisions that differ from your usual template, so the exceptions get attention rather than blending in.
5
Produce a cited analysis. A memo, anchored to the Codification, that a reviewer can check rather than take on trust.

500+

hours saved in six months

$100K+

in advisory fees saved

We use Gaapio's contract analysis constantly for new lease agreements, and it writes most of our technical accounting memos — including our ASC 606 revenue recognition memos and any complex, one-off technical issues that come up.
Controller, CPA

Why the citation trail matters more here than anywhere

Contract analysis is the workflow where a confident wrong answer does the most damage. A misread clause becomes a recognition error, which becomes — at minimum — an uncomfortable audit conversation, and at worst a restatement. This is exactly the objection technical accountants raise about general-purpose AI tools, and it is well founded.

Which is why every conclusion here carries a citation you can click through, and why the system is built to flag ambiguity rather than resolve it silently. You are meant to check this work. It is designed to be checkable.

Frequently asked questions

Legal tools answer what you are obligated to and where the risk sits. This answers what the contract requires you to recognize and when. Different questions, different outputs, different reviewers. Most teams need both.

Bring a contract you have a question about

Ideally one where you are not certain of the answer. We'll walk the analysis with you and show you the citation trail.

Request a Demo Talk to a CPA

References: FASB ASC 606, Revenue from Contracts with Customers; FASB ASC 842, Leases. This page is general information, not accounting advice for a specific entity.

Contract Analysis for Accounting Teams