Loan Ops Ledger
Agent notices matched daily to the loan system, each break classed and explained from the credit agreement before month end.
Rate sets, interest and fee notices, paydowns and PIK capitalisations still reach loan operations by email, fax and portal. We read each agent notice, recompute the amount in code from the credit agreement's own conventions, and match it to your loan system and to the cash your bank reports. Every difference gets a class, an owner and an explanation with the clause cited. The agent's register stays the record of ownership. Your analysts decide what is booked.
Ref AGT-PVS-TL1-20260623 · v1
Received 2026-06-23 11:02 ET
Break class · PIK togglePIK Election dated 12 Jun 2026, at least 10 business days before the 30 Jun payment date; 50% elected, within the 75% cap. Clause §3.02(ii).
The borrower elected to pay half the interest in kind; the loan system still expected cash.
Two records of each loan, kept in step every day
The administrative agent keeps the register of who owns each loan and sends the notices. Your loan operations team keeps its own record in the loan system. That record has to stay in step with the agent's, notice by notice, and with the cash that actually arrives.
- 1Loan operations analystReceives agent notices by email, fax or portal: rate sets, interest and fee notices, paydowns, PIK capitalisations and borrowing requests relayed from the borrower.
- 2Loan operations analystChecks each notice against the loan system: contract type, interest period, benchmark, margin and floor, principal, day count and the amount that results.
- 3Treasury, with the custodianMatches expected cash to bank statement files on each payment date, and chases the agent when a payment is short or missing.
- 4Loan operations leadInvestigates each break with the agent, asks for its calculation, and decides which record needs correcting.
- 5Trade operationsSettles loan trades through a settlement platform; the agent records the buyer as lender of record once the assignment is complete.
- 6Fund accounting, with the fund administratorTies positions, accruals, PIK and fees at month end, and supplies loan data for the fund leverage facility's reporting.
Role titles are indicative.
- Agent notices: rate set, interest, fee, principal paydown, PIK capitalisation
- Borrowing Requests and Interest Election Requests, relayed by the agent
- PIK Election notices, and PIK elections deemed by amendment
- Credit agreements and their amendments
- Loan system exports: contracts, accrual schedules, positions (traded and settled), cash projections
- Bank statement files (BAI2 / BTRS; ISO 20022)
- Settlement documents: trade confirmation, assignment and assumption, funding memo
- Daily match file
- Break report: class, owner, age, explanation, status
- Bookings in the loan system, under the analyst's name
- Queries to the agent, with the agent's replies
- Month-end tie-out to the fund administrator and general ledger
- Loan data for the leverage facility's Monthly Report and borrowing base
The breaks come from contract mechanics, not arithmetic
- 1
A partial PIK election
In one filed amendment the borrower may pay up to 75% of interest in kind, by irrevocable notice at least 10 business days before the payment date. The same amendment deemed PIK elections for three 2025 payment dates, so no notice was ever sent. Miss one and cash, principal and accrual all break at once.
- 2
A day count that looks like a data error
The ARRC recommends Actual/360 for SOFR loans; sterling loans usually accrue on Actual/365, and an agreement can choose otherwise. On a $24.75m loan at 9.5625% for 91 days, the gap between the two is $8,195.26 (illustrative).
Same loan, two day countsPenrose Vale Software TL · 31 Mar – 30 Jun 2026CheckInputsResultInterest at ACT/36024,750,000.00 × 9.5625% × 91/36024,750,000.00 × 9.5625% × 91/360598,253.91Interest at ACT/36524,750,000.00 × 9.5625% × 91/36524,750,000.00 × 9.5625% × 91/365590,058.65Difference598,253.91 − 590,058.65598,253.91 − 590,058.658,195.26Agreement basis, §1.01 "Interest computations" (fictional)360-day year, actual days360-day year, actual daysACT/360 appliesSame loan, same rate, same days. The basis changes the number.
The same fictional loan accrued on two day-count bases; the agreement's clause decides which applies. - 3
The knock-on at fund level
In one filed fund leverage facility, partial PIK loans currently paying in kind are capped at 10% of the pool, and PIK loans paying no cash interest are ineligible. A missed toggle can overstate the borrowing base, and a PIK amendment may need the leverage provider's consent.
- 4
A payment that should never have been sent
In August 2020 an administrative agent meant to pay lenders about $8m of interest and wired about $900m, principal included. The dispute ran until an appeals court ruled in September 2022. The LSTA published a form erroneous-payment provision in 2021.
The model reads. Code computes. Your analyst decides.
Each notice follows the same fixed path. The model reads the notice and drafts explanations. Code does every calculation and every match. A named person decides anything that is booked, disputed or paid.
The model never writes to the loan system, never changes settlement instructions and never releases cash. It cannot accept or dispute an agent's figure. Those decisions sit with your loan operations lead and treasury, under their own names. Where the agent's notice and your ledger differ, the playbook explains the difference. It does not overwrite either record.
Three breaks, three different causes; the agent's figure stands until the agent answers the query.
Every break closes with its reason on file
Each notice leaves one evidence line: where the figure came from, what code recomputed, which rule classed the difference, and who accepted it. Advisers must keep written communications about receipts and disbursements for at least five years, so the notice and the reason sit with the decision.
Kept for every run
- 01The original notice, with its file hash, sender and time received
- 02Each extracted field, with its place on the page
- 03The loan-system snapshot the notice was matched against
- 04The calculation trace: fixing date, rate, days, basis, rounding
- 05The break class, the explanation and the clause cited
- 06The reviewer's decision, any edits, and the time
- 07The prompt version, model version and check results for the run
- 08Booking references and bank statement references
A month of historical agent notices with the breaks you already know about, read access to a loan system export, bank statement files for the same month, and two people who can label the answers.
A fixed workflow, with one read-only loop
Loan Ops Ledger is a workflow, not a free-roaming agent. A router sends each notice down a fixed path. Deterministic engines compute and match. The model reads, classifies and drafts. The one agent loop, break investigation, has read-only tools. This section is written for your engineers and your model-risk reviewers.
- Agent notices: email, fax image, portal extract, agent data feed
- Loan system export: contracts, accruals, positions traded and settled
- Bank statements: BAI2 / BTRS, ISO 20022
- Credit agreements and amendments, conventions versioned per facility
- Daily match file and break report
- Queries to the agent, drafted for the lead to send
- Month-end tie-out to fund administrator and GL
- Run record per notice, kept for audit
Model tools: read · propose. Execute tier (post booking · release cash · change settlement instructions) is not exposed to the model.
The model never decides what is booked or paid; it proposes, and code and people check.
Harness
- Routing, then matching. Notices are routed by type into a deterministic matcher. Anthropic's guidance favours fixed workflows where a task is well defined and has to be predictable. Daily loan operations is that kind of task.
- One bounded loop. Break investigation may query the loan system, past notices and correspondence. It has read-only tools and step and token caps, and it proposes a cause, never an adjustment.
- Engines in code. An expected cash-flow calculator (accrual, day count, lookback, floor, rate reset, PIK split, pro rata share), a matcher with per-field tolerances, and break ageing.
- Typed hand-offs. Everything the model passes to code is a typed record: field, value, unit, date, document, page, span, confidence and extractor version. Structured output guarantees the shape of that record, not its values, so code checks the values too.
Data and integrations
- Agent notices: email text and attachments sent to your designated "Agent Notices" address, faxes received as images, agent portal extracts, and agent data feeds where your agent contributes to one.
- Loan system: contracts, accrual schedules, positions (traded and settled) and cash projections, read through vetted, parameterised queries rather than free-form SQL. Export formats differ by system; we map yours during the assessment.
- Bank cash: BAI2 files (maintained by ASC X9 as BTRS, version 3.2 of April 2020) and ISO 20022 statements.
- Settlement: trade confirmation, assignment and assumption, and funding memo from your settlement platform.
- Credit agreements and amendments: one index per agreement. Each facility's conventions are held as versioned parameters linked to their clauses.
- Fund facility: loan data for the collateral administrator's Monthly Report and for the Borrowing Base Calculation Statement attached to each Notice of Borrowing.
- Cadence: notices daily; cash on each contract's payment dates; tie-out at month end.
What is hard for machines, and what we do about it
Conventions change the number, not the words: day count, lookback fixing dates, business-day rolls.
Encode each facility's conventions once per agreement version and recompute in code. Writing a program instead of computing in text raised accuracy by about 12% on average across eight maths and finance datasets (Program of Thoughts, Codex, 2022).
Notices are laid out differently by each agent, are often scanned, and carry global and per-lender amounts on the same page.
Use layout-aware parsing, then check each figure literally against the text it came from. Tables remain the weak point: in late-2024 tests the best PDF parser scored about 79 of 100 on table structure, and GPT-4o 72 (OmniDocBench).
PIK arithmetic. Elections are partial, some are deemed by amendment and never arrive as notices, capitalised PIK itself bears interest, and cents must round the same way on both legs.
Load elections and deemed elections from the agreement and its amendments, compute the split to the cent with a stated rounding rule, and treat PIK as its own break class.
A daily process needs the same answer every day. gpt-4o solved 61.2% of τ-bench retail tasks in one try, but fewer than a quarter consistently across eight tries (mid-2024).
Measure pass^k on break explanations, keep each model step short, and run the golden set every night.
Sometimes the right answer is that the agent is right and your record is stale.
Never let the matcher overwrite. The explanation says which record should move and why, and a person decides.
How we know it works
- Golden set: synthetic notices covering Term SOFR, Daily Simple SOFR with a lookback, ABR, floors, stub periods, month-end date rolls, partial PIK at 25%, 50% and 75%, deemed PIK, paydowns, fees and delayed settlement. Added to that is a month of your own notices with known breaks, labelled by two of your people independently.
- Metrics, reported per field: extraction exact match; recomputed interest within $0.01 of the agent where conventions match; auto-match rate; false-match rate (a break wrongly closed), held near zero; unexplained-break rate; share of explanations the analyst accepts; pass^k on explanations.
- Release gate: every fortnightly release passes the regression suite, and no field may regress beyond its tolerance. A new model version runs the full golden set, plus a replay of recent notices, before it goes live.
- Shadow run: the playbook runs beside your current process through at least one month end. Your team's record stays authoritative, and every disagreement is logged with its root cause before you accept.
- No public benchmark covers agent notices. Any accuracy figure we give you comes from your golden set, and we say so.
Controls and security
- Tool tiers: the model can read and propose. Execute actions (post a booking, release cash, change settlement instructions) are not exposed to it. They run from the approval screen under the approver's name, in line with OWASP's advice to require human approval for high-impact actions.
- Notices are untrusted input. The component that reads them has no write tools and no network access, and it can only output a typed record. Text inside a notice cannot choose an action. In 2024 tests, limiting tools this way cut targeted prompt-injection success against GPT-4o agents from 47.7% to 7.5% (AgentDojo).
- Bank details never change from a notice. Any email or notice asking for new wire instructions opens a blocked case with a call-back task. The FBI recommends verifying account changes through a second channel. Business email compromise losses reported to it were $2.77bn in 2024.
- Separation of duties: the playbook counts as a maker. The person who accepts an explanation cannot also release the cash.
- Records, not re-runs: every input, prompt version, model version, output and reviewer action is stored, so any result can be reconstructed without running the model again.
The rules this work sits inside
- LSTA Standard Terms, SOFR versionDelayed-settlement cost of carry uses average SOFR on a 360-day basis, plus 11.448bp.
- ARRC statement on LIBOR fallbacksThe fixed spread adjustments apply to fallback contracts, not to new SOFR loans.
- AIFMD II loan-origination rules applyEU loan-originating funds need policies for administering and monitoring loans, reviewed at least annually.
- SR 26-2 and OCC 2026-13 issuedRevised US bank model-risk guidance; generative and agentic AI are outside its scope.
- LSTA private credit model provisions (PCC MCAPs) finalModel credit agreement terms for private credit, based on the BSL MCAPs; members only.
Records: Advisers Act Rule 204-2 (in force) requires written communications about receipts and disbursements to be kept for at least five years.
Terms
- Administrative agent (US) / facility agent (UK/EU, LMA)
- The lender group's agent. It keeps the register, sends notices and distributes payments.
- Agent notice
- Any message from the agent to lenders about borrowings, rates, payments, fees or amendments.
- Rate set
- The agent's notice of the benchmark and all-in rate for an interest period.
- Term SOFR / Daily Simple SOFR
- The forward-looking SOFR term rate, and daily SOFR accrued in arrears without compounding.
- Day count
- How days turn into interest. Actual/360 for USD SOFR loans; Actual/365 is the norm for sterling (US vs UK difference).
- Lookback
- Using the SOFR fixing from a set number of business days earlier, so the amount due is known before the payment date.
- Floor
- The minimum benchmark rate the agreement allows.
- PIK toggle / PIK Election
- The borrower's option to pay part of the interest in kind, added to principal, by notice before the payment date.
- Break
- A difference between your record and the agent's, the custodian's or the bank's that must be explained. A practitioner term, with no formal definition.
- Register / lender of record
- The agent's book-entry record of who owns the loan.
- Assignment and assumption
- The settlement document that transfers a loan interest (US usage; the LMA equivalent was not verified).
- Cost of carry / delayed compensation
- Compensation for a trade that settles late. The LSTA formula uses SOFR (US); LMA terms differ.
Recently updated
- PIK elections recognised as their own break class, with the fund-facility impact flagged.
- Rules and terms on this page reviewed as of 28 September 2026, including SR 26-2 and the LSTA's private credit model provisions.
Questions
No. The agent's register remains the record of who owns each loan, and your loan system remains your book. The playbook reads both, explains where they differ and proposes what should change. Your analyst books any change under their own name. Where the agent's figure needs challenging, your lead raises the query with the agent.
The explanation shows both figures, the recompute, the clause, and which record would need to move. Your loan operations lead decides whether to accept the agent's figure or raise a query. The query, the agent's reply and the decision are kept with the notice. Nothing changes on either side until the agent answers.
When a notice shows interest paid in kind, the break is classed as a PIK toggle and the capitalised amount is recomputed to the cent. The playbook then recalculates the loan's effect on your facility's PIK concentration and eligibility tests, using your facility's own definitions, and flags the result to the fund controller before the next borrowing base report.
Notices are treated as untrusted input, and the component that reads them has no write access and no network egress. Model versions are pinned and named in every run record. We list the model providers and sub-processors for your vendor review, and for EU managers' DORA register of information.
The golden set runs every night and on every change. We track match rate, false matches, unexplained breaks, accepted explanations and consistency across repeated runs. Model versions are pinned, and a new version goes live only after the full suite and a replay of recent notices pass. Providers give at least 60 days' notice before retiring a model.
A mapping session, then a two-week assessment. For that we need a month of historical agent notices with the breaks you already know about, read access to a loan system export, bank statement files for the same month, and two people who can label the answers. Build then runs in fortnightly releases.
