Solutions
Covenant monitoring that stores evidence, not just booleans
Structured JSON for covenant desks watching minimum liquidity and runway triggers with reproducible artifacts.
Covenant systems often store pass/fail booleans without the JSON that justified the decision. Storing Cashytics outputs next to tests gives examiners and borrowers a replayable trail when disputes arise.
Test harness design
Mirror covenant formulas in your engine but attach API outputs as supporting context when rules are judgment-based. Version both formula hashes and API responses on each test date.
When distress and runway disagree, treat that as a workflow trigger — it often signals timing mismatches worth a relationship call before a technical default.
Minimum liquidity and blocked cash
Exclude truly restricted cash per agreement definitions, but document exclusions in metadata so later reviewers understand why balances differ from raw bank totals.
Reporting to borrowers
Share redacted JSON summaries in borrower portals where contracts allow so remediation plans start from shared facts rather than competing spreadsheets.
Audit readiness
Retain envelopes per test period in WORM or immutable object storage when your policy requires non-repudiation. Link objects to loan IDs in your servicing system of record.