In a syndicated financing the credit agreement is the document everyone reads. It is long, negotiated in detail, and its covenants, reporting duties and financial tests get captured in a covenant compliance process because the consequences of missing them are severe and well understood.
The fee letter is a different animal. It is short, it is often signed earlier than the credit agreement, it is frequently subject to tighter confidentiality than the facility documents, and it is sometimes split into several letters addressed to different parties. It also contains most of the dated money obligations in the transaction: arrangement and underwriting fees, agency fees, commitment and ticking fees on undrawn amounts, and conditional amounts payable if the deal takes a different route.
The result is a predictable control gap on both sides of the table. Borrowers pay fees from a spreadsheet maintained by whoever ran the financing, and when that person moves the calculation basis becomes folklore. Arrangers and agents chase accruals across deals with inconsistent day count conventions. Neither party has the fee obligations in the same register as the covenant obligations, which is why reconciliation disputes surface at refinancing rather than at the time.
Why fee letter obligations go untracked
The causes are structural rather than careless, which is why the same gap appears across institutions with otherwise strong documentation controls.
- Separate document, separate custody, the fee letter is filed with the transaction bible or held by a deal team, not in the system that tracks the credit agreement.
- Confidentiality limits circulation, restricted distribution means the people who monitor obligations may not be permitted to hold the letter, so nobody registers its duties.
- Accruing fees need a calculation, not a reminder, a ticking fee on undrawn commitments changes daily with utilization, so a calendar entry alone cannot produce the right number.
- Conditional fees have no date, break and alternative transaction fees depend on an event, and event-triggered obligations are the hardest kind to keep visible.
- Multiple letters, multiple parties, arranger, agent and security trustee arrangements may sit in different letters, and no single view shows the total fee stack.
None of this is hard to fix once the fee letter is treated as a source of obligations rather than as correspondence. The work is extraction and registration, with attention to the confidentiality constraint, and it fits the same discipline already applied to obligation management in financial services generally.
For every accruing fee, capture the rate, the base it applies to, the day count convention, the accrual start and end triggers, the payment dates and the party entitled. A register that holds only an amount and a date will be wrong the first time utilization changes. Where the base is an undrawn or unsyndicated amount, name the system that supplies that figure so the calculation has a documented source rather than an assumption.
A working obligation set for fee letters
Five entry types cover almost every fee letter, and each needs a different monitoring pattern.
- Event-triggered one-off fees. Arrangement, underwriting and upfront fees payable on signing, closing or first utilization. Register the trigger event, the payee and the gross-up or withholding treatment.
- Daily accruing fees. Commitment and ticking fees on undrawn or unsyndicated amounts. Register rate, base, day count, accrual window and the data source for the base.
- Periodic service fees. Agency, security trustee and facility fees payable annually or on defined dates. Register the date, the amount and whether it is payable in advance or arrears.
- Conditional and contingent fees. Break, alternative transaction and flex-related amounts. Register the trigger condition and the calculation, and review at each deal milestone.
- Confidentiality and disclosure duties. Who may receive the letter, what may be disclosed in a syndication memorandum, and any duty to obtain consent before wider circulation.
A five-step roadmap for bringing fee letters under control
Step 1, Inventory the letters per transaction
Confirm how many fee letters exist for each financing and who holds each one. On larger deals it is common to find arranger, agency and trustee arrangements in separate documents with different counterparties and different confidentiality terms.
Step 2, Extract obligations into structured fields
Capture rate, base, day count, trigger, payment date, payee and withholding treatment as fields rather than leaving them in prose. Structured extraction is what allows the accrual to be recalculated when utilization changes.
Step 3, Resolve the confidentiality question deliberately
Decide who may hold the letter and who may hold the derived obligation record. In many cases the obligation fields can be registered with restricted visibility even where the document itself cannot be circulated.
Step 4, Name the source for every moving base
Undrawn commitment, unsyndicated amount and outstanding balance all come from a system. Record which one, so the fee calculation can be reproduced and reconciled rather than reconstructed from memory.
Step 5, Reconcile paid against accrued each period
Run a periodic comparison of fees accrued against fees invoiced and paid, per transaction and per payee. Differences found monthly are administrative. The same differences found at refinancing are disputes.
See fee obligations in the same register as covenants
Rates, bases, triggers and payment dates extracted from fee letters and monitored alongside the credit agreement duties.
What good looks like at refinancing
Refinancing is the moment fee letter discipline pays. A borrower that can produce, in one view, every fee accrued and paid across the facility life, with the calculation basis and the source data for each period, negotiates from a position of fact. A borrower reconstructing the history from bank statements and email threads negotiates from an estimate, and the gap is usually resolved in the arranger’s favor because the documentary record is theirs. The same holds for agents managing a book of transactions: consistent day count treatment and a single source for undrawn balances removes a recurring category of small disputes that consume disproportionate operational time. Neither outcome requires a new system in most institutions. It requires the fee letter to be extracted at closing rather than filed, and its obligations to live where the covenant obligations already live, with owners, dates and a reconciliation cadence. Where the credit agreement duties are already monitored, adding the fee stack is an incremental change to an existing control, in the same way vendor oversight contract controls extend an existing register rather than replacing it.
Fee letter register pattern
The table shows the field set that makes each fee type monitorable rather than merely recorded.
| Fee type | Trigger or cadence | Basis to record | Reconciliation |
|---|---|---|---|
| Arrangement or upfront | Signing or first utilization | Flat amount, payee, withholding | Confirm paid at closing |
| Ticking fee | Daily from signing to close | Rate, undrawn base, day count | Monthly accrual review |
| Commitment fee | Daily on undrawn amount | Rate, base source system | Quarterly against invoice |
| Agency fee | Annual on stated date | Amount, advance or arrears | Annual payment confirmation |
| Break or alternative fee | On defined event | Trigger condition, calculation | Review at each milestone |
Fee letters are short documents carrying a disproportionate share of a financing dated money obligations, and their separateness from the credit agreement is the whole reason they slip. Treating them as an obligation source rather than transaction correspondence closes the gap: inventory every letter per deal, extract the rate, base, day count and trigger into structured fields, decide consciously who may hold the document and who may hold the derived record, name the system that supplies each moving base, and reconcile accrued against paid on a regular cadence. The work is modest and it converts a folklore-driven spreadsheet into a record that holds up at refinancing.
For related guidance, see Vendor contract controls for OCC and FFIEC exam readiness, OCC and FFIEC expectations for vendor contract files and Vendor agreement controls for model risk management.
