One record underneath every deal.
CORA OS is the engine beneath CORA. It maps each deal from its credit agreement into one record, ties each figure to its source and ties each act to a person.
At a glance
Exact to the cent
Money is held exactly as the record states it, never rounded and never approximated.
Signed in securely
SSO and MFA for your team, with customer data never used to train AI models.
Your environment
A shared cloud environment or one dedicated to your institution, encrypted in transit and at rest.
In detail
Read from the agreement, held as one record.
CORA OS reads each credit agreement and holds the deal's terms, reporting and tests in one place, so the screens, the reports, your team and the borrower all work from the same reading.
- Terms, reporting and tests from the agreement
- The same terms on each screen and report
- Lender and borrower on the same reading
Permissions, approvals and a trail of acts.
Who can see, who can act and who must approve are set once by the lender and held across the deals they cover.
- Role-based permissions
- Your own approval tiers with named seats
- An audit trail with who and when
How lenders use it.
Read a covenant
See a covenant's current figure, threshold and cushion, held exact to the cent on the deal's one record.
Trace a figure
Follow a covenant figure line by line to the amounts behind it, so each number ties to its source.
See who did what
See each act on the deal with the person who took it and when.
One platform, built in layers.
Where your team and your borrowers work.
The portfolio desk, a Monitor for each deal, the conversation where CORA reports and asks, and the borrower portal for requests, uploads and signing.
- Today's To-Do's, Needs you and Past Due on one desk
- The borrowing base, rates and covenants for each deal
- Requests, uploads and signatures from the borrower
The model reads, asks and drafts. A person decides.
CORA reads the agreement and the files, raises the judgment calls with a recommended answer and the agreement's words, answers questions from the record with its sources, and drafts the next act for a person to confirm.
- Questions with a recommended answer and the cite
- Answers from the record, with sources named
- Drafts that wait for a person's confirmation
Confirmed rules run in code, to the cent.
Once a rule is confirmed, the engine applies it the same way each period: ineligibles, caps, reserves and availability recomputed from gross, and covenants tested at their dates.
- Exact decimal from the file to the certificate
- The borrowing base recomputed from gross
- Covenants and springing terms tested at their dates
One record per deal, read from the agreement.
The agreement, the configuration drawn from it, the files and the rulings all sit on one record, with each act attributed to the person who made it and the time.
- The configuration, each term with its section
- Files classified and filed by deal and period
- An audit trail of who did what, and when
Questions.
What does one record per deal mean in practice?
The terms, reporting and tests CORA reads from the credit agreement are held once, and the screens, reports and people working the deal read from that same record.
How are amounts held?
Exactly as the record states them, to the cent. Nothing is rounded or approximated along the way.
Who can change a deal's setup?
Whoever your role-based permissions allow, through your own approval tiers where you require them. Each change is on the audit trail with who made it and when.
Where does our data live?
In a shared cloud environment or one dedicated to your institution, encrypted in transit and at rest.
Is CORA SOC 2 certified?
SOC 2 Type I is complete, and Type II is in progress with an independent auditor.
Build on one record.
See one of your own agreements mapped into a record your whole team can work from.