LatestAll news

Home / Use cases / PCT-071

Monitor portfolio · PCT-071 · Sourced card

Spread quarterly packs into one model

Spreads each borrower’s monthly and quarterly pack into one monitoring model, whatever the layout, and flags new or renamed add-backs.

Worked example: The Q2 pack adds a first-time add-back (strategic review fees, $0.6m) and renames another. Both are mapped and flagged. Recomputed leverage 5.29x vs 5.12x on the certificate. See the walk-through ↓

Direct lendingABF / asset-basedSample data · real docs confidentialVendor + in-house
INPUTMonthly packs and compliance certificateAI STEPSRead packs and cert · Map to onetemplate · Track headroom over timeOUTPUTStandard monitoring row with headroomtrendHUMAN CHECKA person reviews and decides

Today vs automated

TODAY
  1. Open each borrower packAnalyst · manual
  2. Re-key into the modelAnalyst · manual, re-keying
  3. Recompute covenantsPM · manual
  4. Email / meeting hand-offAnalyst → PM
AUTOMATED
  1. A borrower’s monthly or quarterly pack arrivesTrigger: starts on its own
  2. Read packs and certAutomated · Document store
  3. Map to one templateAutomated · LLM
  4. Track headroom over timeAI draft, human review · Monitoring model
  5. Whether a gap is a definitional judgment, a timing difference or a reporting problemApprove / override · PM

AutomatedAI draft, human reviewHuman onlyTools: Inbox / portal, Document store, LLM, Monitoring model, Loan system

Estimated valuesourced + estimate

180–3,300 analyst hours a year
$27k–$825k of time, vs an assumed $20k–$100k tool cost

Net: −$73k to $805k a year net of tool cost; at the low end of the assumptions it does not cover the tool cost.

Manual3–6 h per borrower quarterWith AI0.5–1.5 h per borrower quarter, review included
Assumptions
  • 3–6 analyst hours per borrower quarter today; 0.5–1.5 hours with an agent, including review
  • 120–600 borrower quarters a year for one team
  • $150–250 per hour loaded cost
  • Tool or build cost $20,000–100,000 a year (both)

Sourced figures

Estimate, based on the assumptions shown; your numbers will differ. How we estimate

What else it can do for the team

  • Track late or incomplete deliveries per borrower
  • Feed signals into the early-warning brief
  • Pre-fill the quarterly portfolio review
  • Update internal risk ratings
  • Produce the LP portfolio KPI table
Worked walk-throughKey catch: The Q2 pack adds a first-time add-back (strategic review fees, $0.6m) and renames another. Both are mapped and flagged. Recomputed leverage 5.29x vs 5.12x on the certificate.

1. The input

SAMPLE: fictional company, illustrative figures. Not a real borrower, deal or lender group.

Project Meridian’s Q2 2026 monthly pack in the borrower’s own layout, the prior quarter’s spread, and the facility’s EBITDA definition. See the full SAMPLE deal pack →

Q2 2026 monthly pack, EBITDA bridge (SAMPLE, LTM Jun 2026, $m): Net revenue 281.2 · EBITDA (management accounts) 33.2 · Integration costs 1.4 · Recruiting and relocation 1.1 · Legal settlement 0.8 · Strategic review fees 0.6 · Clinic ramp costs 2.3 · Run-rate savings 4.6 · Sponsor monitoring fee 1.2 · DSO 57 days

Borrower’s own layout and labels. The Q1 pack used different line names.

2. What the AI produces

Borrower’s label (Q2 pack)Template lineLTM Mar 26LTM Jun 26MappingFlag
Net revenueRevenue284.0281.2High
EBITDA (management accounts)Reported EBITDA33.933.2HighSum of monthly P&L; the certificate uses 34.1
Integration costsAdd-back: non-recurring1.51.4High
Recruiting and relocationAdd-back: non-recurring1.11.1High
Legal settlementAdd-back: non-recurring0.90.8High
Strategic review feesAdd-back: non-recurringn/a0.6MediumNew this quarter. Not in the QoE or prior packs
Clinic ramp costsAdd-back: de novo losses2.22.3MediumRenamed. Q1 pack called it “De novo clinic losses”
Run-rate savings (billing, procurement)Add-back: run-rate cost savings4.44.6HighWithin the 20% cap
Sponsor monitoring feeAdd-back: sponsor fee1.21.2High
Days sales outstandingKPI: DSO (days)5357HighUp 9 days in two quarters

Covenant row written to the model: recomputed Total Net Leverage 5.29x against 7.00x; the certificate shows 5.12x. Non-recurring items are 11.7% of reported EBITDA, over the 10% cap, so 0.6 is excluded. Line-by-line certificate check →

Monitoring historyQ4 25Q1 26Q2 26
Recomputed Total Net Leverage (covenant 7.00x)4.71x4.95x5.29x
Leverage per certificate4.66x4.88x5.12x
Non-recurring add-backs, % of reported EBITDA8%10%12%
DSO (days)505357

3. What a person still checks

  1. Ask the borrower what the strategic review is (a sale process, a refinancing, a restructuring adviser) and whether more fees are coming. The answer matters more than the $0.6m.
  2. Confirm “Clinic ramp costs” is the same item as last quarter’s de novo losses, not a wider bucket.
  3. Approve the two medium-confidence mappings before the quarter is locked in the model.
  4. Decide whether a rising leverage trend with headroom intact is a watchlist matter.

4. Where it breaks

  • Borrowers change layouts and labels; a silent mis-mapping puts an add-back in the wrong cap bucket.
  • The agent applies the definition it was given; side letters or prior amendments that change caps must be loaded too.
  • Monthly packs are usually unaudited; a gap to the certificate is a question, not a finding.
How you get thereFour steps from prompting to an agentic workflow; most teams start at step 2.
1 · PromptingAn analyst asks a chat tool about one borrower quarter.
Needs: an approved AI tool, a confidentiality policy.
Risk: unchecked answers, data pasted outside policy.
2 · WorkflowA fixed pipeline extracts the same fields into your template every time.
Needs: field definitions, a template, document parsing.
Risk: breaks silently when formats change.
Typical starting point
3 · AgentIt watches the inbox or data room, runs the checks and drafts the output.
Needs: inbox/doc-store access, system write-back, logging.
Risk: acting on a misread; needs review gates.
The automated lane above
4 · Agentic workflowSeveral agents work across the deal or book; people approve exceptions.
Needs: shared data model, permissions, audit trail, exception queue.
Risk: errors compound across steps; needs monitoring.
Solution optionsBuy (21 vendors listed), build or hybrid, with the trade-offs of each.
Build
An LLM API, a document parser, a vector or document store, your data warehouse, and a review queue.
Fits your definitions exactly; you own maintenance and controls.
Hybrid
Vendor extraction feeding your own checks, templates and systems.
Common middle path; two things to integrate and govern.

Listing is not endorsement.

What changes for the team3–6 h → 0.5–1.5 h per borrower quarter (estimate); coverage goes from a sample of borrowers, quarterly to every borrower, every delivery.
ROLESAnalysts move from re-keying packs to reviewing exceptions and calling borrowers.
CYCLE TIME3–6 h → 0.5–1.5 h per borrower quarter (estimate)
COVERAGEFrom a sample of borrowers, quarterly to every borrower, every delivery.
CONTROLSEvery output cites its source; approvals and overrides are logged.
How it works

Full title: Every borrower's quarterly pack, spread into one monitoring model: covenant headroom tracked quarter by quarter

“The Q2 pack added an add-back nobody mentioned and renamed another. The spread catches both.”

Scenario

A portfolio monitoring team receives monthly financials and a quarterly compliance certificate from each borrower and needs them in one standard model, with covenant headroom tracked over time.

What the human still decides

Whether a gap is a definitional judgment, a timing difference or a reporting problem, and whether the name moves on the watchlist.

Why it matters

Monitoring vendors now sell AI ingestion of borrower financials and compliance certificates (Alkymi launched its private credit product in Feb 2026), which says the manual spreading step is where teams feel the load.

What the record shows

Checked 2026-10-18.

Alkymi (Feb 2026) extracts compliance certificates and financial statements and cross-validates ratios against covenants; Equipped describes AI-driven ingestion of borrower financials with covenant tracking; Allvue's Portfolio Intelligence (Jul 2026) adds covenant headroom monitoring.

Try it: prompt and data
You are a private credit monitoring analyst. Using the attached compliance certificate, monthly financials and the facility's EBITDA definition (with caps), produce one row in our monitoring template: revenue, reported EBITDA, each add-back by category with its cap, net debt, covenant ratio and headroom. Recompute the ratio yourself. List every difference from the certificate with the page it comes from. Do not assess credit quality.

Data

Walk-through uses a SAMPLE deal pack: fictional company, illustrative figures. In practice the inputs are your own confidential borrower or fund documents; keep them inside an approved environment.

Who uses it, vendors and build
Segments
Direct lending, ABF / asset-based
Who uses it
Portfolio monitoring analyst, Portfolio manager
Build
Vendor + in-house
In-house
Extraction plus a fixed template; definitions and caps must be configured per facility.
Last verified
2026-10-15

Vendors that claim this capability

Tags reflect each vendor's own public claims at the linked page (checked 2026-10-15). Not tested, ranked or endorsed.

Sources and related

Next step

Not investment advice. Names marked SAMPLE are fictional. Found an error? See the corrections log.