630 likes | 861 Views
Implementing BOG Waivers as Exemptions. Bob Hughes Applications Support Manager North Orange County CCD. About the Presenter. Higher Education Experience – 17 years Whittier College Cal Poly Pomona North Orange County Community College District
E N D
Implementing BOG Waivers as Exemptions Bob HughesApplications Support ManagerNorth Orange County CCD
About the Presenter Higher Education Experience – 17 years Whittier College Cal Poly Pomona North Orange County Community College District Fullerton College, Cypress College, School of Cont. Ed. Banner Experience – 14 years Programming for Financial Aid (Whittier, Cal Poly Pomona) – 10 years MBA CSU Fullerton
About NOCCCD North Orange County Community College District Enrollment (Fall 2010 headcount) Fullerton College (22,354) Cypress College (15,963) SCE (16,613) 2009-10 BOG Waivers: 20,292
What you will learn today How NOCCCD used to award BOG Waivers (as an award) How we do it now (as an exemption) Why we made the change Step through the setup process Lessons learned
A Brief History Banner was implemented in 2001 Pre-2005: BOG waivers were processed manually. Award posted manually on RPAAWRD when completed paper app received. Spring 2005 – on-line application developed Spring 2006 – e-signature, batch posting awards, requirements See our presentation – http://www.3cbg.org/conferences/2006/
Problems with awards Fees not waived (offset) until disbursement occurs Student pays “to be safe”, triggering large number of refunds Student doesn’t pay (expecting BOG), resulting in large unpaid A/R balances Student sees a BOG “award”, expects refund Phone calls to Financial Aid Tedious Reconciliation
Need to improve collections 19% increase in 2 years
The New Way Future plan – use a partial exemption to offset parking; eliminate the nightly adjustment
NOCCD Gavilan Thank you to Dave Phillips Nick Yray CCCConfer Session Archive Available: 4/15/10 “BOG waivers as Exemptions with Gavilan College”
Setup Steps District Division Code Validation (GTVDICD) College Code Validation (STVCOLL) BOG Waiver Year Validation (SVVBGYR) BOG Waiver Terms Definition (SVABTRM) Exemption Authorization (TSAEXPT) Fund Management (RFRMGMT) BOGW Eligibility Type Validation (SVVELIG) BOGW Payment Options Maintenance (SVAPYMT)
Setup Steps (Cont.) BOG Income by Household Size (SVAINCR) BOG Waiver Required Documentation (SVAREQD) Residence Code Validation (STVRESD) BOG Waiver Marital Status (SVVBMTL) Term Control Form (SOATERM)
STVRESD AB 131
Setup is Done! Before you go live: Differences between BOG A, B, C Which ones require documentation? How will you notify re: documentation req’d? Parent signature for BOG B Dependent? Retroactive BOG Waivers Reversing BOG waivers
Populating SVASFND Manually (BOG A, BOG B) Via SVPISIR (BOG B-ISIR, BOG C) – Batch ISIR Process C3SC Use a population selection identifying all recently loaded ISIR records Manual is out of the question for us – we created an “on-insert” trigger on ROBUSDF
After Insert – Payment Process The BOG W payment process can either be called on a single student (via the options drop-down on SVASFND) or in Batch (via SVPPYMT) sv_state_aid_appl_bp.p_bogw_payment_process is the name of the API We automatically call this after each insert for BOG W eligible students
DocumentationReq’d Discovered defect – documentation check box does not prevent payment We added logic in our trigger to bypass the payment process if documentation is required Also bypass BOG B for dependent students (even though BOG B is ‘unchecked’ on SVAREQD)