The Bill Of Obligations

Working With The Bill Of Obligations

I've spent the better part of a decade handling debt instruments and obligation schedules across commercial lending and corporate restructuring, and the moment you actually sit down with The Bill Of Obligations as a working document—rather than reading about it in a textbook—you notice how much the theory glosses over the messiness. The core idea is straightforward: a written schedule that catalogs who owes what, to whom, under which terms, and by when. But the devil is in the amendments, the cross-default clauses, and the part where three different governing laws apply to three tranches of the same facility. Start with the base contract. Before you touch a single line of the bill itself, pull the underlying loan agreement, indenture, or service contract that created the obligation in the first place. I've seen people build entire obligation schedules from secondary sources—term sheets, press releases, board resolutions—and end up with material mismatches that only surface during collection or enforcement. The actual signed agreement almost always contains more specific terms than any summary document. Once you have the primary source, extract the key fields: obligor name and address, principal amount, interest rate structure, payment frequency, maturity date, collateral description, and any events of default or acceleration clauses. Feed those into a structured template rather than a spreadsheet with freeform notes. Template enforcement is what keeps you from missing a subordination layer or an intercreditor boundary. From there, build the bill chronologically. New obligations first, then active ones, then any that are in dispute or near maturity. Group by counterparty when the portfolio allows it, because reviewing one counterparty's full exposure at once tends to surface patterns you miss when you're looking at line items in isolation. I keep a separate column for jurisdiction and governing law because mixed-jurisdiction portfolios introduce a specific headache: you need to track which default remedies are available under which legal framework, and those frameworks don't always align. A clause that triggers acceleration in New York law might not trigger it in English law, and if you're relying on a single master schedule without clear jurisdiction tagging, you'll find out the hard way during a workout.

Edge Case That Cost Me Two Weeks

One time I was reconciling a cross-border syndicated facility where the lead bank had updated the payment waterfall in an amendment but hadn't updated the obligation schedule attached to the security documents. The bill itself said the subordination tier paid after the senior tranche, but the amendment document—the one actually governing the cash flow—had flipped the order for a specific reporting period. I caught it only because I compared the bill against the amendment date by date rather than assuming the bill was current. If I had relied on the bill alone, the enforcement strategy would have been built on a stale waterfall, which in a distressed sale of the underlying asset can mean the difference between recovering forty cents on the dollar and twenty. The workaround was simple in hindsight: attach every amendment as a dated appendix to the obligation schedule and flag any field where the amendment date is later than the bill's last update. Takes about ten minutes per amendment, saves you from having to re-underwrite the whole thing later. First, the most dangerous obligations are the ones that look small. A five-thousand-dollar vendor retainer with a personal guarantee attached often carries more collection risk than a half-million operating loan with full collateral coverage, simply because the guarantee creates a direct path to individual assets and the creditor will pursue it aggressively while ignoring the larger, encumbered loan. Second, obligation schedules decay faster than people expect. A quarterly reconciliation process is the minimum; annual is negligence. I've seen schedules that were technically accurate on paper but months out of date in practice because a payment was waived verbally, a term was modified by email, or a subsidiary was merged without updating the obligor field. The gap between the written schedule and the actual state of affairs is where disputes live. Another thing that trips people up is the assumption that a single bill can handle every type of obligation cleanly. It can't, not really. Financial debt, trade payables, contingent liabilities, and performance obligations each have different measurement and disclosure rules. Blending them into one undifferentiated list produces a document that satisfies no one. Keep the categories separate within the same file, or use linked tabs with clear reference fields, so an auditor or opposing counsel can pull one category without wading through unrelated data.

What The Bill Of Obligations Doesn't Solve

It doesn't resolve valuation disputes. It doesn't replace legal review of enforceability in a given jurisdiction. It doesn't protect you if the counterparty is structurally insolvent and the obligation is unsecured. And in high-leverage situations with intercreditor agreements, the bill is subordinate to the intercreditor deed anyway—if the deed says the senior lender controls the enforcement timeline, your schedule is descriptive, not dispositive. For those cases, you need the underlying agreements and the creditor committee protocols, not just the bill. If you're dealing with a small number of obligations and minimal amendment history, a well-structured spreadsheet is adequate. Once you cross roughly fifteen active obligations with multiple counterparties and any cross-default or intercreditor provisions, dedicated obligation-tracking software or a properly maintained database becomes cost-effective. The break-even point for manual spreadsheet maintenance is usually around forty to sixty hours per quarter in reconciliation and amendment tracking, which most teams can absorb until things get complicated and then the hours compound. The short version of how I'd start if you're building one from scratch: pull the primary contracts, extract the fields I listed above into a template, attach every amendment with dates, reconcile against actual payment records at least quarterly, and keep jurisdiction and category columns explicit. Everything else is polish.