How to create a claims and defenses evidence matrix for Loan Enforcement Disputes

A claims and defenses evidence matrix connects each disputed enforcement proposition to operative loan language, applicable authority, supporting and adverse evidence, witnesses, and unresolved proof gaps. Build it around what counsel must establish or contest—not the order documents arrived. Separate enforcement entitlement, default, notice, acceleration, payment allocation, and claimed amounts. The deliverable is a source-linked working table showing which positions the record supports, which remain conditional, and what evidence or legal research would change the assessment.

When to use this workflow

Use this workflow when lender, borrower, guarantor, or in-house counsel must assess a demand, target discovery, or evaluate evidence before a dispositive motion or hearing. Triggers include disputed acceleration, an unexplained payoff balance, conflicting payment records, or an incomplete assignment chain.

This guide addresses US loan enforcement evidence analysis, not a complete litigation lifecycle. Substantive rights depend on actual documents, governing law, and facts. The cited federal procedural rules concern federal district-court litigation; federal evidence rules apply subject to their applicability provisions. State proceedings, arbitration, bankruptcy, consumer lending, and foreclosure require separate analysis. Confirm the applicable framework before treating a proposition as an element or defense.

What you need

Collect a bounded record containing:

• Executed notes, credit agreements, guarantees, security documents, assignments, amendments, waivers, and forbearances, including incorporated schedules.
• Pleadings, demands, default and acceleration notices, delivery records, and accommodation communications.
• Native servicing ledgers, bank records, rate histories, suspense activity, reversals, collateral recoveries, and claimed-amount calculations.
• Governing-law research, forum rules, and relevant orders.
• Custodian and witness information identifying who maintained accounts, authorized changes, administered notices, and transferred servicing data.

Assign stable document IDs and retain page, clause, or spreadsheet-cell references. Record the review cutoff, missing materials, and whether each agreement is executed and effective rather than a draft or amendment markup. Restrict access to counsel’s analysis and keep it separate from source exhibits intended for production.

Use the template

The companion template is Loan Enforcement Disputes — Claims and defenses matrix. Copy this table into your working document or spreadsheet. Use one row per proposition requiring a distinct evidentiary answer.

“Position” identifies the claim, defense, or disputed issue without prematurely classifying it under substantive law. In “Clause / authority,” distinguish contractual conditions from legal elements and record who bears the relevant burden once researched. Cite the authority and its procedural context; an allegation surviving dismissal is not necessarily proof sufficient for judgment.

Evidence cells need document IDs and pinpoints, not filenames alone. Identify what each source establishes. The witness field records the person and knowledge basis. Use assessments such as supported on current record, contradicted, conditional, or unassessed. Each material gap needs an owner and decision-linked action; include target dates and review history in that cell or a linked record.

Step by step

1. Define the disputed propositions and legal dependencies

Read the demand and pleadings alongside the operative documents. Separate entitlement to enforce, installment nonpayment, notice conditions, acceleration, guarantor liability, and amount. For transferred loans, distinguish evidence of ownership, agency authority, and entitlement to enforce; research which distinctions matter under the applicable law.

Separate facts from legal consequences. A transfer confirmation may establish that funds were sent, not that the installment was discharged. Payment, waiver, modification, and limitations questions need governing-law analysis rather than assumed outcomes.

Record: Row IDs, precise propositions, researched burdens, and unresolved legal dependencies. Do not fill an element field with a rule borrowed from another jurisdiction.

2. Identify controlling language and document versions

Trace each proposition through the effective agreement, amendments, defined terms, and incorporated provisions. For notice and acceleration, check who may act, required content, permitted delivery methods, timing, cure conditions, and any separate election requirement. Record disputed execution or effectiveness.

Avoid generic cure assumptions. The SEC-filed Shift4 agreement’s §7.01(a) distinguishes principal nonpayment when due from interest, fee, or other nonpayment continuing for five Business Days. This illustrates wording only—not a universal cure period or market standard. Annex I contains amendment markup. See the filed agreement, §7.01(a).

Record: Operative version, clause pinpoint, cross-referenced conditions, and missing amendments or schedules. Keep unresolved interpretation in the gap field.

3. Attach supporting and adverse evidence

Test each proposition against both sides of the record. A default notice may establish that a demand was made without independently proving the balance or enforcement entitlement asserted. Pair it with transaction records, delivery evidence, and contrary communications.

Distinguish execution, effectiveness, due date, transfer, receipt, posting, dispatch, cure, and acceleration dates. Link chronology event IDs where available. If sources conflict, preserve both accounts and explain their significance rather than silently choosing one.

Record: Supporting and adverse document IDs, exact pinpoints, and evidentiary limits. Write “not located in reviewed materials,” rather than “never existed,” after an unsuccessful search.

4. Reconcile payment and amount disputes

Break the demand into principal, ordinary interest, default interest, premiums, fees, expenses, and credits. Link each component to its contractual basis, calculation period, rate, and underlying records. Reconcile borrower records with servicing entries, including suspense balances, reversals, effective dates, and recoveries.

Check allocation provisions before applying them. The Shift4 example’s §2.18(b) concerns collateral proceeds received by the administrative agent while an Event of Default exists and loans have been accelerated, subject to intercreditor agreements. It is not a rule for every ordinary payment. See the filed agreement, §2.18(b).

Record: Calculation-cell references, unexplained variances, credit sources, and whether each discrepancy affects default, amount, or both. Preserve reproducible arithmetic; the reconciliation is not a substitute for source records.

5. Identify witnesses and foundation requirements

Ask who can explain each critical record’s creation, custody, processing, and limitations. A relationship manager may know negotiations but not migrated servicing entries. Distinguish personal recollection from document-derived knowledge.

Federal Rule of Evidence 901 requires sufficient evidence supporting that an item is what its proponent claims; witness knowledge and system evidence are illustrative routes. Authentication alone does not resolve hearsay. Rule 803(6) addresses timely, knowledge-based records maintained as a regular practice, with foundation and trustworthiness requirements. Rule 902(11) provides a certification route with notice and inspection safeguards. A ledger’s label alone is insufficient.

Record: Witness or certification plan, knowledge basis, and unresolved authentication, hearsay, or reliability questions, particularly for transferred servicing data.

6. Turn material gaps into focused requests

Prioritize missing evidence that could change a position: transfer documents, suspense-release history, accommodation terms, or delivery proof. Identify likely custodians and systems. Request the specific evidence needed rather than every servicing document.

In federal district-court litigation, Rule 26(b)(1) limits discovery to nonprivileged information relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. Rule 30(b)(6) addresses reasonably particular organizational examination topics, designation, good-faith conferral, and testimony about information known or reasonably available to the organization. Apply the actual forum’s requirements elsewhere.

Record: Request or interview task, linked proposition, owner, and intended decision. Keep service, objections, and response tracking in a linked discovery record.

7. Test assessments and preserve alternatives

Have counsel test each row against the strongest contrary interpretation. Distinguish factual contradiction, missing evidence, unresolved law, and incomplete foundation; each requires a different response. Explain whether the gap could defeat the position or merely narrow it.

Update assessments when new evidence arrives. Preserve prior citations and explain changes. Before motion or hearing preparation, check each selected citation against the proposed exhibit, including native spreadsheet content where relevant.

Record: Current assessment, reasoning, reviewer, review date, and next decision. Close issues only with a stated basis; assign unresolved alternatives expressly.

Worked example

Fictional scenario: All parties, documents, clauses, amounts, and events below are fictional. Counsel for Bay Orchard Components is assessing Alder Quay Finance’s demand under a $3.2 million commercial loan. A June 18 notice accelerates the loan based on an allegedly unpaid $80,000 principal installment due June 10.

Agreement L001 §2.3 sets the due date and directs payment to a designated account. Section 9.2 addresses written amendments; §8.4 addresses collection expenses. Counsel has not resolved their legal effect. A bank confirmation records an $80,000 transfer on June 10; the servicing ledger records an equal suspense credit June 11. Destination-account and suspense-release support remain incomplete. An accommodation email lacks its attachment. The demand includes $18,000 in expenses without invoices in the reviewed production.

The immediate priority becomes tracing the payment, not treating default as established. The matching suspense credit matters, but does not establish destination, effective payment, or proper allocation. The accommodation email justifies targeted collection without proving a modification. Expense support remains independently necessary even if principal liability is established. These three entries illustrate priority issues, not a complete acceleration assessment.

Common mistakes

• One row for “breach.” Separate installment nonpayment, default conditions, notice, acceleration, and amount; proof of one does not establish all.
• Treating a demand balance as proof. Trace components to transactions, clauses, periods, and credits; explain notice-to-ledger differences.
• Recording only favorable documents. Place adverse communications and competing allocations beside supporting evidence.
• Assuming the current servicer explains historical entries. Identify migration records and knowledgeable witnesses for transferred data and adjustments.
• Treating the matrix as a courtroom summary. Federal Rule of Evidence 1006 separately governs evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to originals or duplicates. An internal matrix does not automatically qualify.

Final quality check

• Each proposition permits a distinct evidentiary assessment.
• Contract citations identify operative versions and unresolved document gaps.
• Legal propositions have applicable authority, with burdens and procedural context checked.
• Supporting and adverse citations match source documents and pinpoints.
• Payment rows address credits, reversals, suspense entries, and calculation periods.
• Critical records have foundation plans and identified limitations.
• Material open issues are resolved or assigned to named owners with decision-linked actions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review and evidence analysis can support examination of loan records; its chronology capabilities can help organize dates underlying payment, notice, and acceleration disputes. The matrix remains counsel’s work product, and counsel retains legal and evidentiary judgment. To discuss this workflow, book a demo.

Frequently asked questions

Should lender and borrower counsel use different matrices?

Use the same structure, identifying whose position each row tests. Lender counsel should expose proof gaps; borrower counsel should distinguish genuine contradictions from inconsistencies that do not affect liability or amount.

How detailed should payment rows be?

Separate transactions raising distinct receipt, allocation, or duplicate-charge issues. Keep arithmetic in a linked reconciliation and cite its cells alongside underlying records.

What if governing-law research is unfinished?

Record facts and the proposed proposition, mark the legal dependency unresolved, and assign research. Do not import another jurisdiction’s elements to fill blanks.

When is the matrix ready for motion preparation?

When material propositions have checked sources, adverse evidence, applicable authority, and usable foundation plans—or unresolved issues counsel has expressly assessed. Readiness means no unexplained assumptions, not simply no empty cells.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 30.
• Federal Rules of Evidence, Rules 803, 901, 902, 1006, and 1101.
• Shift4 Payments credit agreement filing, Annex I §§2.18(b), 7.01(a); wording example only.

Source cutoff: October 13, 2026.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.