Ellucian Banner / Colleague Data Validation — Post-Load Reconciliation That Auditors Sign on First Review

Ellucian Banner / Colleague data validation is the post-load reconciliation discipline that proves every record migrated from a Banner or Colleague source landed correctly in the Oracle Fusion target — row by row, balance by balance, hash by hash. For a higher-ed Finance + HR migration, Ellucian Banner / Colleague data validation covers: (1) row-count reconciliation — every Banner FGBJVCD journal voucher, FOBAPPD AP invoice, FGBTRND GL transaction, PHRHIST payroll history record, PEBEMPL employee, PERHIST employment-history record, NBRJOBS job, NBRBJOB base job, PEAFACL faculty appointment, FRBGRNT grant, or Colleague GLA, GENERAL.LEDGER, JOURNAL.SUMMARIES, AP.INVOICES, HRPER, EMPLOYES, POSITION, PROJECTS record reconciled to its target Fusion object; (2) balance reconciliation — every fund balance, every account balance, every grant balance, every AP open-payable balance, every AR open-receivable balance reconciled source-to-target; (3) hash reconciliation — every attached PDF, scanned document, FERPA consent form, signed MPN reconciled by hash; (4) referential-integrity validation — every parent-child relationship preserved (FOAPAL combinations, position-employee, faculty-load-section); (5) exception-record handling — every reject reconciled with documented disposition.

Higher-ed data validation carries a regulatory load that generic ERP migration validation does not. FERPA (20 USC §1232g, 34 CFR Part 99) requires preservation of education records and disclosure logs with audit-grade integrity. Title IV (Higher Education Act, 34 CFR Part 668) requires preservation of federal financial aid award, disbursement, R2T4 and return-of-funds evidence with multi-year retention and Department of Education audit-readiness. IRS 1098-T (26 USC §6050S) requires per-tax-year tuition-statement evidence. IPEDS reporting requires multi-year cohort continuity across Fall Enrollment, Completions, Graduation Rates, Outcome Measures. SACSCOC/HLC/NEASC/WSCUC/MSCHE/ACCJC accreditation requires 5–10 year evidence cycles. GASB (governmental) or FASB (private) requires fund-accounting integrity and capital-asset preservation. Each one of those obligations becomes a specific Ellucian Banner / Colleague data validation acceptance criterion: not 'looks right', but 'reconciles to source with hash-signed evidence the Title IV auditor, the SACSCOC reviewer and the GASB auditor will sign on first review'.

Per domain, Ellucian Banner / Colleague data validation checks: Finance — every Banner FGBJVCD journal voucher reconciled by header and line, every FOBAPPD AP invoice reconciled by header and distribution, every FGBTRND GL transaction reconciled in total and by FOAPAL combination, every fund balance reconciled at month-end, every grant balance reconciled per FRBGRNT, every capital asset preserved with depreciation history; HR — every PEBEMPL employee reconciled to Fusion Worker, every NBRJOBS / NBRBJOB job assignment reconciled to Fusion Assignment, every PEAFACL faculty appointment reconciled with tenure status / rank / contract type, every PHRHIST payroll history record reconciled by gross/net/deduction; Student integration — every Banner SFRSTCR registration record validated against Fusion AR posting, every transcript record validated against the Banner / Colleague archive; Financial Aid integration — every Banner RPRAWRD / RPRADSB award and disbursement record reconciled to Fusion AR posting with Title IV / R2T4 evidence preserved in Banner / Colleague; Advancement — every gift, pledge, constituent record reconciled to Fusion AR posting or to the alternative CRM.

Ellucian Banner / Colleague data validation runs continuously through extract-transform-load development (typically 12–24 weeks) plus a focused 4–6 week pre-cutover validation cycle plus a 2–4 week post-cutover validation cycle. During ETL development, each migrated domain (Finance, HR, Grants, Advancement, Student integration, Financial Aid integration) ships with its own validation suite — row-count, balance, hash, referential-integrity, exception-record checks. The pre-cutover validation cycle runs against a full mock-cutover load with the Controller, AVP HR, Sponsored Programs Office, Registrar, Financial Aid Director and accreditation liaison reviewing reconciliation evidence per domain. The post-cutover validation cycle runs against the production-cutover load with day-1, day-7, day-30 reconciliation milestones. Final sign-off comes at the day-30 milestone with audit-grade evidence handed to the Provost, CFO, CIO and Board's audit committee.

The Ellucian Banner / Colleague data validation evidence pack — handed to Provost, CFO, CIO, Controller, AVP HR, Sponsored Programs Office, Registrar, Financial Aid Director, accreditation liaison, General Counsel, internal audit and the Board's audit committee — contains: a row-count reconciliation matrix per Banner table or Colleague file → Fusion object with deltas explained; a balance-reconciliation pack per fund, account, grant, AP open-payable, AR open-receivable with month-end-balance sign-off; a hash-reconciliation report for every attached binary; a referential-integrity validation report for every parent-child relationship (FOAPAL combinations, position-employee, faculty-load-section); an exception-record disposition log for every reject; a Title IV / R2T4 / 1098-T evidence preservation attestation; a GASB / FASB fund-accounting integrity attestation; a SACSCOC / HLC / NEASC accreditation evidence continuity sign-off; a FERPA disclosure-log integrity verification; an IPEDS continuity attestation per survey; and a signed attestation from each accountable officer that every record landed correctly.

Most Banner-running institutions maintain a Banner Operational Data Store (ODS) for reporting, with downstream campus data warehouses, Cognos / Tableau / Power BI dashboards, IPEDS reporting jobs, NSC enrollment-reporting jobs and accreditation evidence pulls running off the ODS. Colleague-running institutions maintain Colleague Reporting with similar downstream consumers. Ellucian Banner / Colleague data validation reconciles every Banner ODS / Colleague Reporting query against its Fusion equivalent (Fusion OTBI, Fusion BI Publisher, or a successor warehouse) post-migration: every IPEDS Finance / HR / Fall Enrollment / Completions / Graduation Rates / Outcome Measures query reconciled, every NSC enrollment-reporting query reconciled, every accreditation cohort-evidence query reconciled, every dashboard validated by the IR/IE office. The reconciliation evidence is signed by the IR/IE office before the Banner ODS / Colleague Reporting tier is retired.

FERPA-controlled records require special handling during Ellucian Banner / Colleague data validation. The validation team operates under the same FERPA legitimate-educational-interest scope as production Banner / Colleague users, with role-based access scoped per domain, immutable disclosure logging for every record accessed during validation, and sealed-record (under court order or institutional sanction) access limited to the Registrar, General Counsel and authorised judicial officers. Reconciliation evidence is produced at the aggregate level (row counts, balances, hashes) rather than the per-student level wherever possible; per-student validation evidence is preserved with FERPA-compliant access controls and used for exception-record investigation only. The Title IX Coordinator signs the Title IX-restricted partition validation. The Registrar signs the FERPA-controlled partition validation. The Financial Aid Director signs the Title IV-controlled partition validation.

Reconciliation deltas at cutover are expected and handled through a documented exception-record process. The Ellucian Banner / Colleague data validation framework distinguishes between: (1) reconcilable deltas — explained by Fusion-specific data model differences, currency-rounding rules, or known transformation rules — documented with disposition; (2) exception records — reject records that did not load due to data-quality issues — held in a reject staging area with disposition per record (corrected and reloaded, archived as historical-only, written off with sign-off); (3) hard-stop deltas — material variances in fund balance, grant balance, AP / AR balance, payroll gross/net, FERPA disclosure log integrity — trigger a cutover hold and a documented remediation cycle before go-live. The Controller, CFO, AVP HR, Sponsored Programs Office, Registrar, Financial Aid Director and accreditation liaison each have specific delta-tolerance acceptance criteria per domain, signed in advance, with hard-stop authority over their respective domains.