Pre-Financial-Close Audit Checklist
Executive Summary
Key Takeaways
- ✓ Model audit is frequently a formal condition precedent to financial close, meaning a transaction cannot legally close until the audit is complete and the required deliverables are in lenders' hands.
- ✓ The model version reviewed in the audit must be locked and demonstrably identical to the version referenced in transaction documentation, since any drift between them invalidates the audit's relevance to the closing model.
- ✓ A pre-financial-close audit checklist is a coordination and documentation checklist as much as a technical one — timing, deliverable completeness, and sign-off chain all matter as much as the underlying model testing itself.
- ✓ Missing or incomplete audit documentation at close is a common and avoidable source of delay, since it is discovered only when conditions precedent are being formally checked off.
Objective¶
This checklist verifies that the model audit workstream required as a condition precedent to financial close is genuinely complete: the audit has been performed on the correct, final model version, its deliverables are in the required parties' hands, and any material findings have been remediated and re-verified. It exists as a distinct checklist because financial close introduces coordination and documentation requirements that a technical audit checklist alone does not cover.
Model audit is frequently written into financing documentation as a formal condition precedent, not an optional best practice. This checklist treats the transition to close as its own discipline: confirming that what was audited is what is actually closing, and that the paper trail proving this exists before the close date arrives.
Applicability¶
Applicable to any financing transaction, most commonly project finance and structured lending, where independent model audit is a stated condition precedent to financial close. Used by borrowers and sponsors coordinating the closing workstream, and by lenders confirming the condition has been genuinely satisfied before releasing funds.
Checklist¶
| # | Check Item | Why It Matters | Evidence to Collect |
|---|---|---|---|
| 1 | Model audit scope matches the scope defined in the facility agreement or term sheet | An audit performed to a narrower scope than contractually required does not satisfy the condition precedent | Facility agreement audit scope clause, audit engagement letter |
| 2 | The model version audited is confirmed identical to the model version referenced in closing documentation | Any drift between the audited and closing model versions invalidates the audit's relevance to what is actually closing | Version hash or file comparison confirming identity |
| 3 | All material findings from the audit have been remediated and re-verified before close | Closing with an unresolved material finding defeats the purpose of the condition precedent | Remediation log with re-verification sign-off |
| 4 | A formal audit certificate or equivalent deliverable has been issued and provided to all required parties | Lenders frequently require an explicit certificate as documentary evidence the condition precedent is satisfied | Signed audit certificate |
| 5 | Debt sculpting, DSCR, and LLCR mechanics have been specifically verified against the closing facility terms | These are the mechanics most directly tied to the lender's pricing and sizing decision and warrant explicit closing-stage confirmation | Covenant mechanics verification record |
| 6 | The audit trail (who reviewed what, when, and with what result) is documented and retrievable | An audit without a retrievable trail cannot be relied upon if its conclusions are later challenged | Audit working papers, reviewer sign-off log |
| 7 | Model documentation (assumptions book, methodology notes) accompanying the audited model is complete and delivered | Missing documentation undermines the usability of the audited model for the lender's own ongoing monitoring | Model documentation pack |
| 8 | Named individuals or firms responsible for the audit are identified and their sign-off is recorded | Accountability for the audit conclusion should be traceable to a specific, named responsible party | Sign-off record with named reviewer |
| 9 | Any conditions attached to the audit sign-off (e.g. subject to a specific pending item) are explicitly resolved before close | A conditional sign-off left unresolved at close is functionally an incomplete audit | Resolution record for any conditional sign-off items |
| 10 | Closing checklist cross-references the audit deliverables against the full list of conditions precedent | Confirms the audit workstream is tracked alongside, and reconciled against, every other closing condition | Master conditions precedent tracker |
| 11 | Timeline for audit completion relative to the scheduled close date has sufficient buffer for remediation of any late-stage finding | Audits scheduled too close to the close date leave no time to remediate findings without delaying the transaction | Audit and closing timeline |
Common Failures¶
- Audit performed on a model version that was subsequently revised before close, with no re-verification against the final closing version.
- Audit certificate issued with an unresolved conditional item that is never formally closed out before funds are released.
- Material finding identified late in the process and accepted as a known issue rather than remediated, undermining the purpose of the condition precedent.
- Audit scope narrower than what the facility agreement actually requires, discovered only when lenders' counsel reviews the closing documentation.
- Model documentation pack incomplete at close, leaving the lender without adequate reference material for ongoing covenant monitoring.
- Audit workstream timeline compressed against the close date, leaving no realistic buffer to remediate and re-verify any finding.
Recommended Evidence¶
A completed pre-financial-close audit workstream should be accompanied by a signed audit certificate, a remediation log for any findings, and a model documentation pack delivered alongside the audited model. The table above is structured for direct use in a closing checklist or condition precedent tracker, allowing each item to be checked off with its supporting evidence referenced directly.
How to Use This Checklist¶
Coordinate this checklist against the master conditions precedent tracker for the transaction, working backward from the scheduled close date to ensure sufficient time for remediation of any finding. Confirm model version lock early, since discovering a version mismatch close to the scheduled close date is one of the most common sources of delay. See the Lender Model Review Checklist for the underlying technical review this checklist assumes has already been performed, and Project Finance Model Audit for the broader methodology.
Continue Reading¶
Related Pillars¶
Related Glossary¶
Related Checklists¶
Related Case Studies¶
- Infrastructure Lender Catches DSCR Error Before Financial Close
- Bank Syndicate Standardises Model Audit Across a Loan Portfolio
Related Resources¶
Related Products¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is a condition precedent, and how does model audit relate to it?
A contractual condition that must be satisfied before a lender releases funds. Independent model audit is frequently included as one of these conditions in financing transactions, meaning close cannot occur until it is complete and its deliverables are provided.
What does model version lock mean, and why does it matter before close?
Confirming that the exact model file reviewed in the audit is the same file referenced in the facility agreement and closing documentation, verified by file hash, version log, or equivalent. Any unreconciled difference between the audited and closing model versions invalidates the audit's relevance.
What is a model audit certificate?
A formal deliverable, sometimes explicitly required by lenders, certifying that a defined audit scope has been completed and documenting its findings, often required as evidence the condition precedent has been satisfied.
Who is responsible for completing this checklist?
Typically the borrower or sponsor's finance and legal teams coordinate it, working with whichever party performed the model audit, to ensure all required deliverables are assembled before the scheduled close date.
What happens if a material finding is discovered close to the scheduled close date?
It should be remediated and re-verified before close proceeds; closing with an unresolved material finding defeats the purpose of the condition precedent and exposes the lender to the very risk the audit was meant to catch.
How is this checklist different from the lender model review checklist?
The lender model review checklist covers the technical content of what to check in the model itself, principally debt and covenant mechanics. This checklist covers the process and documentation required to satisfy the audit condition precedent as a whole, of which the technical review is one component.
Does this checklist apply outside project finance transactions?
The core logic — audit completion, version lock, sign-off, documentation — applies to any financing transaction with a model audit condition precedent, though the specific technical checks referenced draw most heavily from project finance and structured lending.
What if the audit was performed on an earlier model version than the one used at close?
The audit should be re-run or specifically re-verified against the closing version; findings from an earlier version do not reliably apply to a model that has since been revised.
Related Articles
What Is a Financial Model Audit?
A financial model audit is an independent, structured examination of an Excel based financial model to confirm that its mechanics, logic, and outputs are reliable enough to support a decision. It is not a check of whether the assumptions are optimistic or conservative. It is a check of whether the model actually calculates what its author believes it calculates. Every year, lenders extend debt, investment committees approve capital, and boards sign off on transactions using numbers that came out of a spreadsheet nobody outside the immediate deal team has independently verified. A financial model audit exists to close that gap before it becomes expensive.
What Is a Project Finance Model Audit?
A project finance model audit is a financial model audit applied to the specific class of model used to finance infrastructure, energy, and long dated capital projects: debt sculpted, multi decade, cash flow driven structures with mechanics that do not appear in a typical corporate model. It is frequently a formal condition of financial close, not an optional check, and lender requirements for it exist almost entirely inside non public bank credit policy rather than any single consolidated public source. This page defines what makes project finance models structurally distinct, why lenders require independent verification of them specifically, and what the audit process looks like in this context.
Audit vs Validation — What's the Difference?
Financial model audit and model validation are frequently used as interchangeable terms, and specifying the wrong one in a lender requirement or an internal policy leads to real confusion about what has actually been checked. They test different things. An audit tests whether a model's mechanics are correct. Validation tests whether the model's methodology and assumptions are appropriate for its intended purpose. Both are legitimate, useful exercises. They are not substitutes for each other.