Executive answer
A financial defense file is not a folder containing an agreement, benchmark and annual study. It allows a reviewer to reconstruct, from decision date through payment or amendment, why the transaction existed, who decided, each party’s alternatives, which risks it controlled, how amount and price were set and whether conduct confirmed the agreement.
It should cover loans, facilities, guarantees, cash pools, hedges, factoring, extended balances and treasury charges according to the actual universe. Each transaction needs an identity and audit trail. Cross-cutting documents—policy, organization, authorities and accounting—should connect without duplicating contradictory versions.
The most useful file is built through the lifecycle rather than after an information request. Contemporaneous evidence distinguishes actual decision-making from hindsight and reduces the risk that treasury, tax, legal and accounting present different figures.
Layered architecture
| Layer | Question | Evidence |
|---|---|---|
| 1. Universe | Which transactions exist? | inventory, ledger, banks, agreements |
| 2. Purpose | Why were they entered? | request, budget, use of funds |
| 3. Authority | Who decided and had authority? | powers, committee, minutes, workflow |
| 4. Delineation | What happened economically? | FAR, flows, rights, conduct |
| 5. Capacity | Could each party bear and pay? | statements, scenarios, rating, capital |
| 6. Pricing | What would independent parties agree? | search, comparables, adjustments, range |
| 7. Execution | Was it observed? | drawdowns, payments, covenants, hedges |
| 8. Tax | Which requirements and limits applied? | withholding, computations, returns |
| 9. Reconciliation | Do all records agree? | ledger-study-return bridge |
| 10. Change | Which events required review? | alerts, waivers, amendments |
A missing layer does not always invalidate the transaction, but it identifies where to investigate and improve prospectively.
Complete inventory
Start with data independent from contracts. Extract interest, debt, bank, related-party, derivative, fee, guarantee, receivable, payable and FX accounts. Cross-check bank confirmations, treasury, minutes and filings. Search for unlabeled transactions: overdue balances, payments on another entity’s behalf, unpaid dividends or cash sweeps.
Assign an ID to every instrument and record entities, relationship, currency, principal, dates, rate, reference, security, purpose, balance, interest, withholding, owner and status. For a cash pool detail positions by participant and relevant day or period. For factoring identify each cohort.
Reconcile the population with the annual study and schedules. Explain exclusions. A defense file addressing five agreements where the ledger shows eight counterparties immediately raises a question.
Purpose and origination
Retain the prior request, budget, liquidity need, investment and alternatives. Demonstrate that amount, term and currency fit the use. Link refinancing to prior debt and settlement. For a debt-funded dividend assess capacity before and after.
Minutes should reflect actual information rather than boilerplate. Identify attendees, conflicts, reviewed documents, conditions and vote. Term sheets and negotiations explain why covenants, security and price were chosen.
Record conditions precedent: agreement, authorizations, account, certificates, residence, security or benchmark. If funding preceded completion, explain chronology and effect rather than backdating.
Delineation and capacity
For a loan include cash flow, supportable principal, maturity, amortization, rating and support. For a guarantee include incremental benefit, enforceable obligation and guarantor capacity. For a cash pool include leader functions, structural balances and benefit allocation. For a hedge include exposure, decision and underlying contract.
The FAR should name people and decisions. “Treasury manages risk” is insufficient. Retain reports used, authority, competence and escalation. Test financial capacity through scenarios consistent with those approved.
Document realistic alternatives for both parties. An external quote is not mandatory in every case, but the analysis should identify available choices and why each party accepted terms.
Pricing file
The benchmark should be reproducible: cutoff date, database, strategy, filters, included and rejected comparables, adjustments, range and point selection. Retain an export or evidence permitted by the license; a screenshot of the result is insufficient.
Connect rating to statements and characterized principal. Connect currency, term, seniority, security and date to comparables. Calculate all-in yield including fees. For floating references archive the curve and spread at origination and fallback mechanism.
For a model preserve formulas, inputs, sources and review. For guarantees show floor and ceiling; for factoring, expected cash flow; for cash pools, rates and synergy. Document uncertainty and sensitivity.
Agreements and legal consistency
Retain signed agreement, schedules, translations, security, notices and amendments. Verify legal entities, powers, accounts, currency, amounts, definitions, dates, governing law, tax, payment, events, information, covenants and dispute provisions.
The agreement should implement term sheet and pricing. A different rate, larger principal or omitted security requires correction or analysis. Control versions so that two documents are not both marked final.
Legal should summarize rights and enforceability, particularly for guarantees, subordination, assignments and insolvency. Signature is not the same as enforceability.
Zugzwang can turn scattered documents into an indexed, reconciled Finance Defense File ready to answer transaction-level questions.
Execution evidence
Reconcile drawdown to bank, principal and ledger. Calculate interest through a reproducible calendar, days, reference, spread and balance. Tie payment, withholding and remittance. Record capitalization, prepayment, fees and FX differences.
Monitor covenants and certificates. For a breach retain alert, information, decision, waiver, fee, security and plan. Reaction demonstrates creditor conduct. An extension requires updated capacity and pricing on its date.
For cash pools test sweeps, interest, limits and settlements and identify structural balances. For derivatives retain tickets, confirmations and offset against exposure. For factoring trace invoice, collection, recourse and servicing.
Mexican tax layer
Prepare a requirement-and-consequence matrix covering arm’s length, documentation, withholding, treaty, beneficiary or applicable conditions, deductibility, thin capitalization, net interest, back-to-back credits, tax invoices/support, accounting and filings. Do not mark “compliant” without a reference.
Retain Article 28 Sections XXVII and XXXII computations where relevant, interest carryforward registers, evidence and certificates. Reconcile with the arm’s-length amount; one limitation does not replace another.
Review FX, fees, guarantees and derivatives under the applicable provision and facts. Accounting labels do not determine tax classification. Document positions and legal review.
Reconcile figures
Build a table by ID showing opening principal, movements, closing principal, rate, accrued interest, paid interest, withholding, TP adjustment, nondeductible amount, FX and filing. Every figure should point to a system and document.
Reconcile contractual and local currency and explain rates and dates. Align the study, Local File, Anexo 9 or applicable obligations, ISSIF/SIPRED where relevant, annual return and notes. Do not copy figures without testing periods.
Define materiality for investigation rather than omission. Small repeated differences can reveal a systemic fault.
Index and version control
Use a stable structure: ID / year / 01-origination / 02-capacity / 03-pricing / 04-legal / 05-execution / 06-tax / 07-reconciliation / 08-changes. Name files by date and version. Maintain an index with owner, status and hash or equivalent control.
Restrict editing of the final file but retain working papers. Record reviewer and date. Link master documents rather than copying versions and preserve a snapshot of policy and organization in force that year.
Retention should follow the Federal Fiscal Code, Income Tax Law and applicable rules. Prevent deletion of source data during migrations. Test retrieval annually.
Response readiness
Before an audit, simulate questions for each transaction: existence, principal, rating, method, comparables, support, payments, limitations and reconciliation. Assign spokesperson and evidence. Separate legal, economic and data responses.
Do not deliver an entire repository without a map. Prepare a short narrative, timeline, index and relevant attachments. Ensure every response uses the same version. Log delivery, date and recipient.
Where evidence is missing, do not manufacture historical documents. Identify alternative sources—banks, emails, systems or third parties—describe the limitation and improve controls prospectively. Assess risk before making a claim.
Adversarial review
An independent reviewer should try to disprove:
- that debt exists rather than equity;
- that principal was repayable;
- that the entity controlled risk;
- that rating and comparables were contemporaneous;
- that a guarantee produced benefit;
- that a cash pool allocated synergy;
- that payments and covenants were observed;
- that tax limitations were computed correctly;
- that figures agree across filings;
- that amendments responded to facts.
Record finding, impact, owner, action and date. Do not close a gap based only on oral explanation.
Illustrative case
A group has a loan, guarantee and cash pool involving Mexico. The study shows one rate but the agreement another; principal increased without approval; the cash pool has a three-year debit balance; the guarantee was never invoiced; and the annual return reports different interest.
The defense-file process does not add a memorandum to conceal differences. It separates transactions, reconstructs chronology, recalculates capacity and pricing by date, determines adjustments and limitations, corrects permitted reconciliations and establishes controls. The index marks contemporaneous evidence versus later analysis.
The outcome may include positions to defend and exposures to remediate. That transparency is stronger than a voluminous file without traceability.
Annual calendar
At origination: purpose, capacity, term sheet, pricing, agreement and approval. Monthly: balances, interest, payments and exceptions. Quarterly: covenants, rating triggers, cash-pool permanence, guarantees and forecasts. At year-end: updated benchmarks where appropriate, tax limitations, reconciliation and filings. At an event: reassessment.
Assign a RACI. Treasury produces movements; accounting reconciles; tax computes; transfer pricing analyzes; legal validates; CFO approves. A file coordinator confirms closure.
Minimum deliverable
The defense file should include an executive index, transaction map, timeline, risk matrix, instrument sheets, primary support, models, agreements, execution, tax matrix, reconciliation, findings and update log.
A competent third party should reproduce the conclusion without depending on the file’s original author.
Gap and priority matrix
Classify each requirement as complete, inconsistent, missing or not applicable. Add economic impact, likelihood, deadline and owner. A missing document is not the same risk as unsupported principal; a version difference is not equivalent to an out-of-range rate. Prioritize by effect and by whether legitimate correction remains possible.
Separate contemporaneous remediation from later analysis. Before year-end an approval may be executed, a due fee invoiced, a data error corrected or an agreement prospectively amended where facts permit. Later, a minute must not be manufactured or dated backward. A subsequent memorandum may explain existing evidence if clearly labeled.
The committee should accept residual positions. Record who decided to defend, adjust or disclose, under which advice and with which reserve. The dashboard should remain through closure rather than disappearing when the study is delivered.
Model and data controls
Maintain a field dictionary showing system, table, account, currency, sign, date and transformation. Preserve the original extraction and a working copy. Every manual adjustment needs reason, author and review. Protect formulas and use opening-balance-plus-movements-equals-closing-balance checks.
Test completeness and accuracy through samples from bank to ledger, agreement to system, computation to entry and return to support. For volume data test control totals, duplicates, gaps and out-of-period dates. Document system limitations.
Rating and benchmark models need version, source, parameters and a separate reviewer. An uncontrolled macro or renewed database without a snapshot prevents reproduction. Archive only material allowed by licenses while retaining enough evidence of search and selection.
Information-request rehearsal
Run a test package with ten questions, a shortened deadline and a reviewer who did not prepare the analysis. Measure time to locate evidence, reconcile a figure and approve the response. Log contradictions and reliance on particular individuals.
Include an unexpected question: late payment, uncharged guarantee, rejected comparable or currency difference. This tests the system rather than only the index. Close findings with evidence and repeat after a migration or team change.
Access and confidentiality governance
Define permissions by function and sensitivity. Agreements, bank data, ratings and databases may contain confidential or licensed information. Avoid distributing open folders by email. Log access, downloads and external deliveries.
Restricted access should not prevent continuity. Appoint backups and an offboarding protocol. The Mexican entity should obtain required group information within the response deadline rather than depend on an informal, ownerless request.
Management reporting
Report coverage by transaction value and risk, not only document count. A dashboard may show instruments complete, principal reconciled, interest tested, covenants monitored, filings tied and open findings. Include aging of exceptions and next trigger.
The CFO should see cash and tax exposure alongside documentation status. Legal should see unsigned or unenforceable terms. Treasury should see overdue actions. This converts the file from an annual archive into a control mechanism.
Do not use a green percentage to hide one material red item. Name the transaction, decision needed and deadline. Preserve prior dashboards to demonstrate that the organization monitored and acted.
Sources and cutoff
This article was verified as of August 2, 2026. Consult the current Mexican Income Tax Law, the current Federal Fiscal Code, the OECD Guidelines 2022, particularly Chapters I, V and X, the OECD financial transactions guidance and the OECD Mexico profile.
Zugzwang’s Finance Defense File organizes purpose, capacity, pricing, agreements, conduct, tax and figures into a defensible, maintainable financial file.