Real Estate AI agent · Loan covenants
Loan Covenant Compliance & Reporting AI Agent
Compute each tested ratio under the loan's own definitions, trace every input to the statement it came from, and hold the certificate pack for the named officer, who signs and delivers it.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Officer signs
- Pre-signature
- After launch
- Agent Care
What this agent does
Traces the ratio, never certifies it
In
- 01
A loan enters the portfolio, and its covenant, reporting and reserve clauses are pulled from the executed documents.
- 02
A clause is carried forward with its section number quoted, because no two filed agreements number these alike.
Reason
- 03
A quarter closes, and each tested ratio is computed under the loan's definitions, with each adjustment labelled.
- 04
A carve-out schedule is read against the property's state: Michigan and Ohio void post-closing solvency triggers.
- 05
A statement is built on the accounting method the loan names, which is not GAAP by default in every agreement.
Decide
- 06
A month lands below a sweep threshold, and the consecutive-month count is raised from the first, not the third.
- 07
A certificate falls due on the date its own clause sets, and the pack routes to the named officer who signs.
Out
- 08
A pack goes out under that signature, and the clause, the workings and the sign-off stay on the loan record.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The mortgage and title agent works origination; this one works the life of the loan — and a named officer of the borrower signs the certificate and delivers it.
Example workflow
One loan, clause to certificate
- 1Reporting date reachedLoan agreement, operating statement, rent roll and reserve statements
- 2Obligations extractedCovenants, reporting deliverables and defined terms, each with the clause that imposes it
- 3Covenant computedTested ratios, labelled adjustments, headroom and confidence
- 4Controls appliedDefinition checks, tie-out checks, calendar and consecutive-month checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is certified or delivered at any of them — the agent is computing, and the officer's lane opens at the confidence gate.
Goes to the named officer to sign.
Adds a treasury read first.
Officer sign-off
The pack is held with its workings, its exceptions and the confidence.
Sign · Query · Send to treasury review
Signed — released to deliver
- 6Loan record updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedRestated calculations, exception outcomes, dates met and post-signature corrections
Queries
Each officer query is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Certifying that a covenant is met, or that no default exists.
- Delivering the pack to the lender or the servicer.
- Deciding that an exception has been resolved.
- Agreeing a waiver, amendment or forbearance with the lender.
Automation boundary
Agent acts unaided
- ✓Extract each covenant and reporting clause verbatim.
- ✓Compute the tested ratios under the loan's own definitions.
- ✓Trace each input back to the statement and the ledger behind it.
- ✓Flag what the officer should weigh, and hold the pack for them.
The agent never certifies and never transmits; delivery stays the borrower's act.
- Drawing on a reserve or instructing a disbursement.
- Deciding what a carve-out reaches in a given state.
- Restating a delivered calculation or a signed certificate.
- Changes to definitions, calendar or threshold configuration.
Example output
One covenant test, annotated
Everything the agent computes is attached to the statement it came from — and servicer and securitisation reporting is out of scope, sitting with the banking vertical.
Covenant output · single loan
Illustrative example- Loan
- Single-asset office loan
- Tested covenant
- Debt service coverage on the lender's defined income, tested forward
- Consecutive months
- Month 1 of 3
- Statement of record
- Operating statement
- Confidence
- 91%
- Exception status
- Listed for the officer, not resolved
As received
Taken from the operating statement and the loan agreement on file — nothing on this side is asserted by the agent.
Evidence used
- Operating statement
- Trial balance tie-out
- Loan agreement clause
Why this is flagged
The lender computes this one forward and on its own adjustments;.
What the score decides
Below the configured threshold the pack picks up a treasury read before it reaches the officer.
Action
SignQuerySend to treasury reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every loan
From the loan document
Compute from the clause
Draw on the executed documents and the statements on file, and compute on the definitions the loan itself sets.
The lender computes, you evidence
Routine monthly and quarterly packs arrive computed and traced to their statements.
See the test before it lands
A first month below a threshold or a tie-out break is marked, so the officer sees it while a month can still change.
Build an evidence trail
The ratio, the statement it came from and the officer who signed stay on the certificate.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Property accounting
- Yardi Voyager
- MRI
- RealPage
- Sage Intacct
Asset management
- Argus Enterprise
- Dealpath
- Juniper Square
Loan documents
- SharePoint
- Box
- iManage
- NetDocuments
Agent
Covenant compliance & reporting
- Reads the clause
- Computes the covenant
- Holds for signature
Treasury and reporting
- Kyriba
- GTreasury
- Workiva
- Excel packs
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the certificate
Six tests, run outward to inward. What they jointly miss appears in the map beneath it.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a pack may stand
- L3
- Puts the certification in an officer's hands
- L4 – L5
- Keep the ratio and the statement behind it
- L6
- Holds the certificate at unsigned when signals degrade
How Nestack evaluates it
Evaluate the computation workflow — not only the closing ratio.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the certificate the lender reads
- E1Final-output evaluationDid each ratio use the loan's defined terms and the stated period?
- E2Step-level evaluationDid the agent use the right loan, statement set and definition configuration?
- E3Tool evaluationDid it read the correct loan and the correct reporting period?
- E4Confidence calibrationDo low-confidence packs actually attract more officer queries?
- E5Slice evaluationHow does performance change across specific loan types?
- E6Business outcomeHow many packs needed a query or a correction after signature?
Floor — the outcome the borrower answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, placed at the stage where each one begins.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- FV-03
Definition not extracted
The loan's adjustment terms are never read.
Stage gathers
Loan documents, statements, rent rolls and reserves
02 · Reasoning
2 modes
- FV-04
Trailing-period test
A forward-looking test is run on trailing actuals.
- FV-06
Management NOI used
The income the loan defines is never derived.
Stage proposes
Ratios, adjustments, headroom and confidence
03 · Tool / write
2 modes
- FV-02
Consecutive month missed
The first month below a threshold passes unremarked.
- FV-05
Rent roll and statement split
The two are pulled from different extraction dates.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- FV-01
Statement does not tie
The operating statement does not agree to the trial balance.
Stage returns
The pack the officer signs and the servicer reads
05 · Change / Version
1 mode
- FV-07
Silent definition drift
A model or config change narrows what is flagged.
Stage tracks
Model, prompt, loan definitions and calendar
- Sev-1 · acts on the lender pack
- Sev-2 · a wrong ratio reaches the certificate
- Sev-3 · a statement degrades, pack holds
Affected slices
One loan can carry most of the exposure
A portfolio-level delivery-timeliness figure can read clean while a few loan types absorb most of the restated calculations. Nestack reports the restated-calculation rate by loan type, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Cash-swept floating-rate loans | 7.9% | 3.7× | Review | |
| Mezzanine and A/B structures | 5.8% | 2.7× | Review | |
| Multi-property crossed loans | 4.0% | 1.9× | Watch | |
| Fixed-rate single-asset loans | 2.6% | 1.2× | Normal |
Bar: restated-calculation-rate lift vs. fixed-rate single-asset baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
No cycle ends until a case exists
A cycle closes when the late delivery is a regression case. That suite is what the next certificate assembled is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Restated calculations rise in one loan type.
- 02
Diagnose
The coverage figure the lender had already computed, and the loan calls final, is traced back to the adjustment nobody applied.
- 03
Improve
The fix carries a number, and the loans that forced it travel with it.
- 04
Verify
Nothing goes out until every touched loan case has passed again.
- 05
Learn
It is kept permanently, and the covenant rules are amended alongside it.
Learn → Detect
The return edge. The next quarter computes 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, covenant workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Covenant workflow discovery and boundary definition.Week 1
- 02Statement and loan-document assessment.Week 1, Week 2
- 03Loan definition, calendar and reserve-rule mapping.Week 1, Week 2
- 04Statement ingestion and normalisation.Week 2
- 05Covenant logic and evidence binding.Week 2, Week 3
- 06Confidence scoring and exception routing.Week 3
- 07Officer sign-off workflow.Week 3, Week 4
- 08Accounting and document-system integration.Week 5
- 09Delivery and calculation cases.Week 4, Week 5
- 10Guardrails and officer controls.Week 4
- 11Loan-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final 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 tier | PilotOne loan, one lender | ProductionProduction statement feeds | AdvancedMultiple lenders / entities |
|---|---|---|---|
| Introduced at Pilot | |||
| Computation to your loan and clauses | ✓ | ✓ | ✓ |
| Officer sign-off | ✓ | ✓ | ✓ |
| Calculation-trace baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by loan | — | ✓ | ✓ |
| Sign-off workflow in your systems | — | ✓ | ✓ |
| Approved internal write-back | — | ✓ | ✓ |
| Statement-and-loan integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-lender definition sets | — | — | ✓ |
| Multi-stage borrower approvals | — | — | ✓ |
| High loan volume | — | — | ✓ |
| Multi-lender delivery controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your loan documents and their amendments
→Clause extraction and covenant mapping
Week 102Representative statements and rent rolls
→Computation baseline, definition mapping and evidence binding
Week 203Your reporting calendar and reserve schedules
→Loan definition and calendar mapping, and the boundary
Week 104Access to relevant systems, statements or exports
→Accounting and document-system assessment, then integration setup
Week 205Certificates you would not want tested
→Delivery cases and the evaluation suite
Week 406What no compliance certificate may state
→Confidence scoring, exception routing, guardrails and sign-off controls
Week 307Named officers to review the pack
→Officer sign-off workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Time on the job fixes each band here, which is why one week in the middle carries a pair of them.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Covenant workflow discovery, definition mapping and the automation boundary
W2Statement integration and the computation baseline
W3Covenant workflow, confidence logic and sign-off controls
W4Evaluation suite, delivery cases and failure-mode testing
W5Document integration, pilot loans and targeted corrections
W6One reporting quarter run under the finance officer, then Agent Care handover
- Reading the band
- Each band covers the weeks its work is named in and no others. The week 5 overlap is real, not padding.
- At the end of W6
- The final checks clear on live loans and monitoring moves to Agent Care.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a covenant-compliance agent around your loan documents.
Bring the loan agreements, the statements behind them and the reporting calendar. A named officer of the borrower carries the compliance certificate — that officer signs it, delivers it and answers for it long after the fact, and the agent only shows the workings.
- Typical delivery
- 4–6 weeks
- Deployment
- Your loans and statements
- Officer signs
- Pre-signature
- After launch
- Agent Care available
Nestack Agents · Covenant compliance
AGT-RE-22 · Agent Care available after launch