This article is a work in progress. If you have any questions, thoughts, or corrections, contact us.

Transaction agreements

Document coordination

status: draft

Document coordination

A typical ABF transaction has 5-15 core documents that reference each other constantly. Reading each document in isolation is dangerous. This guide covers how to coordinate across documents, catch inconsistencies before they become problems, and maintain document integrity throughout the deal lifecycle.


status: draft

Why cross-references matter

The biggest documentation trap is treating each agreement as standalone. In practice:

  • The Credit Agreement defines “Event of Default,” which includes a “Servicer Default” as defined in the Servicing Agreement
  • The Servicing Agreement defines modification limits, but the consequences of exceeding them are in the Credit Agreement
  • The Sale Agreement defines eligibility criteria, but the advance rate haircuts for concentration breaches are in the Credit Agreement
  • The Account Control Agreement governs cash, but who can give instructions and when is determined by the Credit Agreement

A single defined term may appear in 5 documents with slightly different meanings in each. A trigger level may be set in one document but the remedy determined in another.


status: draft

Creating a cross-reference map

Before signing, build a systematic cross-reference inventory.

Step 1: List all cross-references

For each document, identify every reference to another document or a term defined elsewhere.

Source DocumentReference TypeTarget DocumentTarget Section/Definition
Credit AgreementDefined termServicing Agreement”Servicer Default” (Section 5.1)
Credit AgreementTriggerSale Agreement”Eligibility Criteria” (Schedule A)
Servicing AgreementConsequenceCredit AgreementEvent of Default provisions
ACATriggerCredit Agreement”Event of Default” definition

Step 2: Verify consistency

For each cross-reference, confirm:

  • The referenced section/definition actually exists
  • The language matches what’s expected
  • Any incorporated terms are consistently defined

Step 3: Document discrepancies

When you find inconsistencies, document them in a single issues list:

IssueDocumentsDiscrepancyResolution
Delinquency triggerCredit Agreement vs. Servicing Agreement60+ days vs. 90+ daysAlign to 60+ in both
Servicer Default definitionCredit Agreement vs. SSADifferent cure periodsSSA controls per CA Section X
Eligible ReceivableSale Agreement vs. Credit AgreementSA has additional criteriaAdd to CA or clarify SA controls

status: draft

Defined terms concordance

Many cross-reference problems stem from defined terms. A concordance tracks every defined term across all documents.

Building the concordance

TermDocumentDefinitionConflicts
Eligible ReceivableSale Agreement[full definition]More restrictive than CA
Eligible ReceivableCredit Agreement[full definition]Less restrictive than SA
Servicer DefaultServicing Agreement[full definition]Includes cure periods
Servicer DefaultCredit AgreementCross-reference to SSA-
Event of DefaultCredit Agreement[full definition]-
Event of DefaultACACross-reference to CAVerify cross-ref is correct

Common definitional conflicts

Conflict TypeExampleResolution Approach
Different thresholdsDelinquency defined as 60+ days in one doc, 90+ in anotherPick one; incorporate by reference
Different cure periodsServicer Default curable in 30 days (SSA) vs. 15 days (CA)Longer period controls
Different inclusionsMaterial Adverse Change broader in CA than NPANarrow definition controls
Circular definitionsA references B, B references ARewrite to break circularity

Which definition controls

When definitions conflict, the documents should specify which controls. Common hierarchies:

  1. Primary document controls: “In the event of conflict between this Agreement and any other Transaction Document, this Agreement shall control.”
  2. Defined terms in one document: “All capitalized terms used herein shall have the meanings set forth in the Credit Agreement unless otherwise defined herein.”
  3. Most restrictive controls: “Where definitions differ, the more restrictive definition shall apply.”

If the documents are silent, you have ambiguity. Resolve before signing.


status: draft

Common cross-document problems

Circular definitions

“Available Funds” means all Collections less the Servicing Fee. “Collections” means all amounts received by the Servicer and deposited in the Collection Account. “Servicing Fee” means [X]% of Collections.

Problem: You cannot calculate Available Funds without knowing Collections, but Collections affects the Servicing Fee which is deducted to get Available Funds.

Fix: Work through calculations manually with actual numbers before signing. Rewrite circular definitions.

Timing mismatches

DocumentRequirement
Servicing AgreementServicer delivers data by 5th business day
Administration AgreementCalculation Agent delivers report by 3rd business day
Credit AgreementBorrower delivers borrowing base certificate by 5th business day

Problem: The calculation agent cannot produce a report before receiving the data.

Fix: Build timeline dependency into the drafting. Servicer delivers Day 3; Calculation Agent produces Day 5; Borrower certifies Day 7.

Trigger mismatch

The Credit Agreement triggers an Event of Default if the Delinquency Trigger is breached. The Servicing Agreement defines Delinquency Trigger. But the definitions use different measurement dates (month-end vs. payment date).

Problem: You may be in default under one document but not the other.

Fix: Align measurement dates. Specify which definition controls for Event of Default purposes.

Inconsistent amendment thresholds

DocumentAmendment Requires
Credit AgreementMajority Lenders (50%)
Servicing AgreementControlling Party (as defined in CA)
ACABank, Depositor, and Secured Party

Problem: Amending the servicing standard requires Majority Lenders under the Credit Agreement, but the Servicing Agreement says Controlling Party. If Controlling Party is defined as Required Lenders (66%), you have a conflict.

Fix: Define amendment thresholds in one place; incorporate by reference elsewhere.


status: draft

Document negotiation workflow

Phase 1: Initial drafts

Capital provider’s counsel produces first drafts of all documents simultaneously. Review all documents as a package, not individually.

Key actions:

  • Create cross-reference map immediately
  • Identify defined terms concordance issues
  • Note timing dependencies
  • Flag obvious inconsistencies

Phase 2: Markup and turns

Your counsel marks up documents. Each turn creates risk of new inconsistencies.

Key actions:

  • Track changes across all documents, not just the one being marked
  • When you change a definition in Document A, check if it affects Document B
  • When you add a carve-out in one place, consider if it should appear elsewhere
  • Maintain running issues list

Phase 3: Pre-signing review

Final review before execution. This is your last chance to catch problems.

Key actions:

  • Refresh cross-reference map against final documents
  • Walk through key calculations with actual numbers
  • Verify all cross-references still work (sections may have been renumbered)
  • Confirm defined terms concordance is clean

Phase 4: Post-closing maintenance

Documents may be amended during the deal’s life. Each amendment creates new cross-reference risk.

Key actions:

  • When amending one document, check impact on others
  • Update cross-reference map after amendments
  • Verify defined term changes flow through correctly

status: draft

Pre-signing checklist

Consistency checks

  • Defined terms are used consistently across all documents
  • Trigger levels match the term sheet
  • Financial covenant calculations work with your actual numbers
  • Cross-references between documents are accurate (section numbers, defined terms)
  • Amendment thresholds are consistent or hierarchy is specified
  • Cure periods are consistent or more favorable controls
  • Measurement dates are consistent
  • Reporting deadlines create a feasible timeline

Calculation tests

  • Borrowing base formula produces expected result with sample data
  • Waterfall calculation distributes funds correctly
  • Financial covenants can be satisfied based on projections
  • Trigger calculations are achievable with headroom

Structural verification

  • True sale language is consistent across all documents
  • Security interest grants cover all intended collateral
  • UCC filings will be made in correct jurisdictions
  • Account control agreements cover all required accounts
  • Intercreditor provisions are consistent across all documents

status: draft

Document coordination pitfalls

Last-minute changes

A provision is changed in the Credit Agreement the night before closing. No one checks whether it affects the Servicing Agreement. After closing, you discover a conflict.

Prevention: Final document changes require cross-document review. No changes to one document without checking others.

Section renumbering

During drafting, sections are renumbered. Cross-references become wrong. The Credit Agreement references “Section 5.1 of the Servicing Agreement” but Section 5.1 is now Section 6.1.

Prevention: Use defined section names (“the ‘Servicer Termination Section’ of the Servicing Agreement”) rather than section numbers where possible. Final check of all cross-references.

Orphaned definitions

A defined term is deleted from one document but still used in another. The second document now references a term that does not exist.

Prevention: Defined terms concordance. Search for term across all documents before deleting.

Multiple versions

During negotiation, multiple versions of documents circulate. The signed Credit Agreement references the March 15 version of the Servicing Agreement, but the signed Servicing Agreement is the March 22 version.

Prevention: Version control discipline. Clear file naming. Final closing checklist confirming document versions.


status: draft

Tools for document coordination

Issues list

A shared spreadsheet tracking every open issue across all documents:

Issue IDDocument(s)Issue DescriptionOwnerStatusResolution
1CA / SSADelinquency trigger mismatchOriginator counselOpenAwaiting CP response
2AllAmendment threshold inconsistencyCP counselResolvedCA hierarchy controls

Defined terms index

A master list of all defined terms across all documents:

TermWhere DefinedWhere UsedNotes
Eligible ReceivableSA Schedule ACA, SA, SSAIdentical in all
Servicer DefaultSSA Section 5.1CA, SSACA incorporates by ref

Timeline chart

A visual showing when each document requires action:

DayServicerCalculation AgentBorrowerTrustee
T+3Data to CA---
T+5-Report to Borrower--
T+7--Certificate to Agent-
T+10---Distribution

Closing checklist

A comprehensive list of all documents to be executed, all filings to be made, and all conditions to be satisfied:

ItemDocumentStatusResponsible PartyDue Date
Execute Credit AgreementCAPendingAll partiesClosing
File UCC-1-PendingCP counselClosing +1
Deliver legal opinionTrue salePendingOriginator counselClosing

status: draft

After closing: maintaining coordination

Amendment protocol

When amending any document:

  1. Review impact on other documents
  2. Consider whether other documents need conforming amendments
  3. Update cross-reference map
  4. Update defined terms concordance
  5. Circulate updated materials to all parties

Regular audits

Annually or at major lifecycle events:

  1. Verify all cross-references still work
  2. Confirm defined terms are still consistent
  3. Check that calculation methodologies match current practice
  4. Review whether any document provisions have become stale

Version tracking

Maintain a master document log:

DocumentOriginal DateAmendment 1Amendment 2Current Version
Credit AgreementJan 15, 2024Mar 1, 2024-Amendment 1
Servicing AgreementJan 15, 2024--Original
Sale AgreementJan 15, 2024Mar 1, 2024Jul 1, 2024Amendment 2