Financial Review Checklist Yale

STANDARD OPERATING PROCEDURE: Institutional Financial Review Checklist (Yale Framework)

1. Document Control Block

• Document ID: SOP-FIN-YALE-094
• Effective Date: October 24, 2023
• Version: 3.4.1
• Review Cadence: Annual
• Owner: Office of the Chief Financial Officer & Template Registry Architecture Group

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the mandatory operational protocol for conducting institutional financial reviews under the Yale Financial Framework. The objective is to ensure absolute fidelity in capital allocation tracking, general ledger (GL) reconciliation, variance analysis, and endowment draw compliance. Adherence to this protocol is mandatory for all divisions executing financial audits or monthly close procedures within institutional or endowment-backed portfolios.

---

3. Scope & Prerequisites

3.1 Scope

This procedure applies to all operating units, auxiliary funds, sponsored research accounts, and endowment funds managed under the institutional umbrella.

3.2 Prerequisites & Required Access

• Software Systems: Oracle Financials Cloud (GL/AP/AR modules), Workday Adaptive Planning, Hyperion Financial Management (HFM), and institutional data warehouse querying tools.
• Credentials: Active Financial System Administrator or Controller-level Role-Based Access Control (RBAC).
• Reference Documentation: Current fiscal year budget allocations, endowment spending rate resolutions, and Chart of Accounts (COA) mapping keys.
• PPE/Physical Security: N/A (Digital Information Systems).

---

4. Roles & Responsibilities

---

5. Step-by-Step Procedure

Phase 1: Data Extraction & System Reconciliation

• 1.1 Initiate the monthly financial data pull from Oracle Financials Cloud across all relevant fund codes (1000–9999).
• 1.2 Verify trial balance equilibrium; confirm that total debits strictly equal total credits ($\Delta = $0.00$).
• 1.3 Reconcile cash and cash-equivalent clearing accounts against external bank statements via automated ingestion logs.
• 1.4 Flag any unposted journal entries or suspense account balances exceeding the $$1,000$ materiality threshold.

Phase 2: Endowment & Restricted Fund Compliance Check

• 2.1 Cross-reference endowment distributions against the Board-approved spending rate policy.
• 2.2 Audit restricted gift accounts to ensure expenditures strictly align with donor-imposed stipulations and legal covenants.
• 2.3 Verify that underwater endowment funds (where market value is below historic dollar value) have appropriate payout restrictions applied per institutional guidelines.

Phase 3: Budget Variance Analysis (Yale Model)

• 3.1 Import actual expenditures into Workday Adaptive Planning and compare against YTD budgeted baselines.
• 3.2 Compute absolute and percentage variances for all major operating categories (Personnel, Equipment, Indirect Costs, Subcontracts).
• 3.3 Isolate variances exceeding $\pm 5%$ or $$50,000$ (whichever is lower) for mandatory root-cause investigation.
• 3.4 Draft explanatory variance narratives for all flagged line items, obtaining operational sign-off from department heads.

Phase 4: Final Sign-Off & Archival

• 4.1 Compile the complete financial review package into the institutional document repository with cryptographic checksum validation.
• 4.2 Secure electronic sign-off from the Department Controller via the enterprise workflow engine.
• 4.3 Archive audit trails, ledger snapshots, and working papers in read-only cold storage for the mandatory 7-year retention window.

---

6. Quality Assurance & Pro-Tips

6.1 Best Practices

• Automate Reconciliations: Utilize pre-built API connectors for bank feeds to eliminate manual transcription errors during Phase 1.
• Materiality Thresholds: Do not spend excessive operational cycles investigating minor variances under the $$1,000$ threshold unless systemic anomalies are suspected.

6.2 Common Pitfalls

• Timing Mismatches: Failing to account for accrued expenses versus cash-basis disbursements can falsely trigger variance alerts in Phase 3. Always run reports on an accrual basis.
• COA Misclassification: Ensure cross-charges between operating and capital budgets are executed within the correct accounting period to avoid skewed departmental performance metrics.

6.3 Metric Thresholds

• GL Variance Tolerance: $\le 0.00%$ discrepancy between sub-ledger and general ledger totals.
• Audit Closure Velocity: Complete all four phases within $T+5$ business days post-month-end close.

---

7. Frequently Asked Questions

Q1: What is the mandatory protocol if an unresolvable variance is discovered during Phase 1 reconciliation?
A1: Immediately isolate the transaction batch, notify the Department Controller in writing, and log an incident ticket within the financial systems management queue. Do not force-balance the ledger using artificial suspense entries.

Q2: How are multi-year grants handled within the monthly Yale framework checklist?
A2: Multi-year sponsored awards must be evaluated on both a current-year budget baseline and a cumulative life-of-project trajectory to ensure burn rates do not prematurely exhaust external funding streams.