FINANCE
Portfolio monitoring reads the facility, the test and the numbers, then flags what is near a threshold. Analysts see the clause. They do not reassemble the spreadsheet the night before the test date.
Banking teams track hundreds of facilities across emails, side letters and personal reminders.
Facility 17 / Q3 leverage test
Reminder queued. No breach flag.
Covenant tests, baskets and notification dates are pulled from the documents and run against the numbers you already receive.
Incoming compliance certificates are checked against the facility. Exceptions are queued. The rest is logged.
The same monitoring can sit with a borrower’s team: which test is next, which input is missing, which notice has to go out.
MONITORING
The ratio, the definitions and the testing date come from the facility. The calculation shows its inputs. A near-miss is flagged before the certificate is due.
Interest periods, clean-down dates and notice windows leave personal calendars and land on the facility.
A compliance certificate is read, compared with the last one and the document, and parked when a number does not tie.
THE RECORD
Amendments, waivers and side letters stay attached to the facility they change. The test uses the document that is actually in force.
Every flag records the clause, the figures and the person who cleared or escalated it.
When a test fails or a notice is required, the matter opens with the document already attached. Legal is not forwarded a spreadsheet.
Definition, ratio and the period it covers.
Where each number came from.
The facility version the test used.
Who accepted the result or escalated it.
01
Observe
02
Map
03
Build
04
Run
05
Expand
Four to six weeks to the first production workflow, on your documents from day one.
No. It reads the documents and the numbers you already store, and writes the test result and the exceptions back.