CREx OS · Credit

Debt and credit portfolio analytics on the same OS as your equity book

Whole loans, mezzanine, preferred equity, bridge, and construction should not live in a separate spreadsheet stack. CREx OS runs credit portfolio analytics beside multifamily and commercial: loan book and maturity ladder, covenant testing, DSCR trends, watchlist, and lender reporting packages built from trusted data. Agentic Asset Management is included so covenant monitoring and exception work have a named owner every month.

What is CREx OS debt and credit analytics?

CREx OS debt and credit analytics is the credit pillar of CREx OS: loan-level and portfolio views for CRE credit strategies, fed by governed data and worked by Agentic Asset Management. You get loan book and maturity visibility, covenant compliance testing against actual loan terms, watchlist and risk rating support, debt service and DSCR trends, and lender reporting packages. Where property performance feeds the credit view, certified PM feeds keep collateral ops data current. Agents handle mechanical monitoring. Named operators escalate what needs judgment. CREx sits above servicing systems; it does not replace origination or loan servicing.

Why spreadsheets fail

The debt workbook fails the same way the equity pack fails

Credit teams inherit the same failure modes equity AM teams know well. CREx OS treats credit as a first-class asset class in the same operating system, with the same close discipline.

01

Terms drift from the model

The loan agreement says one thing. The monitoring file says another. Nobody notices until a test fails late.

02

Collateral data arrives late or wrong

Rent rolls and NOI that feed DSCR come from third-party managers on different systems. Without certified feeds and someone working exceptions, covenant tests run on stale inputs.

03

Maturity and concentration hide in tabs

Ladder charts look fine until a cluster of expirations and a soft submarket show up in the same quarter.

04

Lender packs are rebuilt

Each request becomes a project. Provenance is unclear. Reviewers ask which version is current.

Coverage

Credit reports and monitoring included

Out of the box for the credit pillar. Custom credit views are built by your Agentic AM operator as part of the license.

Credit coverage
  • Loan book and maturity ladder
  • Covenant compliance and testing
  • Watchlist and risk rating support
  • Debt service and DSCR trends
  • Lender reporting package
  • Interest and fee accrual views
  • Valuation and IRR context at ownership
  • Debt summary joined to the equity book
Covenant monitoring

Loan covenant monitoring with a named owner

One Agentic AM capability inside CREx OS delivery is loan covenant monitoring, continuous. DSCR, LTV, and reporting covenants are tested against your actual loan terms, not a copied cell in a workbook. You hear that a covenant is trending toward a breach while there is still time to act. The lender package is built from the same numbers the test used.

Agents

Mechanical monitoring

  • Refresh tests when feeds and loan terms update
  • Flag breaches and near-breaches
  • Assemble supporting schedules for the lender pack
Operators

Judgment and sign-off

  • Interpret borderline cases
  • Coordinate with your team and servicers or PMs as needed
  • Sign what goes to the lender

Software can compute a ratio. Accountability for the story still needs a person.

AI auditability

Agents propose. Named humans approve. The trail stays with the loan

Credit and private credit buyers need AI that accelerates monitoring while leaving a trail a lender or IC member can follow. Agentic Asset Management on CREx OS runs that way by default.

AI auditability on CREx OS debt means agents propose covenant tests, watchlist moves, and package drafts; named humans approve what becomes official; and every material figure keeps source-data documentation back to loan terms and certified PM feeds. Cell-level and package sign-off record who approved what and when. Lender packs are assembled from the same governed numbers the tests used, so provenance is not a second project.

Agents

Propose and assemble

  • Refresh covenant tests when loan terms or collateral feeds update
  • Flag breaches, near-breaches, and missing inputs
  • Draft supporting schedules for the lender pack
  • Surface source links: loan clause, feed as-of date, property financials
Named humans

Approve and sign

  • Interpret borderline cases and watchlist moves
  • Approve or reject proposed adjustments
  • Sign cell-level changes where policy requires it
  • Sign the package before it reaches the lender

Software can compute a ratio. Accountability for what you send a lender still needs a name.

Who changed an input
SpreadsheetA cell edit with no owner
CREx OSNamed approver, timestamp, and reason on the change
Where NOI came from
SpreadsheetA pasted tab from last month's email
CREx OSLineage to the certified PM feed and as-of date
Which terms were tested
SpreadsheetA copied schedule that drifted from the agreement
CREx OSTests bound to the loan master in the OS
What the lender received
SpreadsheetA rebuilt pack with unclear version
CREx OSPack from approved governed figures with package sign-off

Private credit and CRE credit teams get proposal versus approval separation, retained history, and Agentic AM operators who treat sign-off as part of delivery. Agentic AM is included with the CREx OS license. Where DSCR depends on property performance, certified PM feeds and exception queues keep collateral inputs from becoming an undocumented guess inside a test.

If the open role is mostly keep the covenant workbook current, document sources after the fact, and rebuild lender packs, you are hiring for auditability theater. Move the process onto governed data with proposal/approval controls and keep hiring for credit judgment and borrower strategy. Related: alternatives to hiring another CRE analyst.

Trusted inputs

Certified PM feeds where collateral performance matters

Many credit decisions depend on property performance sitting under the loan. That performance often comes from third-party property managers.

CREx OS pulls certified PM feeds on a daily cadence into the same governed environment as your loan master. Freshness monitoring and Agentic AM exception work keep the NOI and rent roll inputs behind DSCR from going quiet without notice.

You are not asked to trust a dashboard that never names a broken source. See property manager integration for how feeds land.

Operating model

Software, agents, people, process on the credit book

01 / Software

One place with equity

Holds loan terms, tests, and portfolio views in one place with your equity assets.

02 / Agents

Recurring checks

Run recurring covenant checks, freshness watches on related feeds, and package assembly.

03 / People

Watchlist judgment

Decide watchlist moves, interpret edge cases, and sign lender materials.

04 / Process

Calendar cadence

Repeats on your reporting calendar so quarter-end is a review, not an archaeology dig.

That is Agentic Asset Management on CREx OS for credit, included with the license.

Hire vs platform

Before you hire another analyst to own the debt file

If the open role is mostly keep the covenant workbook current and rebuild lender packs, you are hiring for a process problem. CREx OS moves that process onto governed data and Agentic AM. Keep hiring when you need more credit judgment and borrower strategy capacity. Do not hire primarily to babysit maturity tabs. Related: alternatives to hiring another CRE analyst.

FAQ

Frequently asked questions

Ask about your loan book.

Does CREx OS replace our loan servicing system?
No. It is portfolio analytics and monitoring at ownership or credit-manager level. Servicing systems and PM systems keep doing their jobs. CREx sits above servicing: it governs the portfolio view and the reporting cadence.
Which credit strategies are covered?
Whole loans, mezzanine, preferred equity, CMBS-related monitoring needs, bridge, and construction are in the credit coverage model. Scope the exact structures in your book on a demo.
Can equity and credit sit in one environment?
Yes. Multifamily, commercial, and credit run in one CREx OS record with asset-class-aware reports.
How does Agentic AM help on debt?
Agents run mechanical monitoring and assembly. Your named operator owns covenant narrative, exception chase on related property feeds, and sign-off on lender packs, on your calendar. See Agentic Asset Management.
Do we need property-level PM feeds for every loan?
Where DSCR and collateral performance matter, yes, certified PM feeds (or governed file paths) keep tests honest. Pure corporate or non-property credit structures can still use the loan master and covenant tools; we scope data sources per book.
Is this a new product SKU?
No. It is the credit pillar of CREx OS. Agentic AM delivery is included with the platform license, scoped to portfolio shape.
Does AI auto-approve covenant results or lender packs?
No. Agents propose tests, flags, and draft schedules. Named humans approve material changes and sign packages before they leave. That separation is the auditability model.
What does cell-level sign-off mean on the credit book?
When policy requires it, overrides and adjustments to inputs that affect tests or reported figures need a named approver before they flow into portfolio totals. Package sign-off covers the full lender or IC set.
Can we show source-data documentation for a DSCR figure?
Yes. Figures carry lineage to loan terms and, where collateral performance feeds the test, to certified PM feeds with as-of context. Exact field-level UI is scoped on demo against your book.
Will this satisfy our auditors or lender reporting policy?
CREx OS provides the control pattern: proposal versus approval, retained history, source documentation, and reproducible packs. Your counsel and credit policy still define what "good" means for your vehicles. We show the trail; we do not claim a blanket regulatory certification badge.
Is auditability a separate SKU?
No. It is part of how Agentic AM runs on the credit pillar of CREx OS. Delivery is included with the platform license, scoped to portfolio shape.
/ Scope credit

Send a summary of your loan count, structures, and monitoring process.

We will show the credit report set on CREx OS and how covenant monitoring would be staffed.

  • Loan count and structures in the book
  • Current covenant monitoring process
  • Whether collateral PM feeds are in play
  • A reply from a CREx operator within one business day
/ Send it to us
Next step

Credit analytics on the same OS as equity.

Book a demo with your loan book shape and monitoring pain points.

Book a demo → Full platform