1. Overview of Forms 486 and 500 Fall 2000

2. Form 486 Receipt of Service Confirmation Form uRevised form dated April 2000 uTo be filed only after: n Funding Commitment Decision Letter has been received n Service has started/will start in July

3. Purpose of Form 486 1. Green light for invoices 2. Certification that technology plans have been approved

4. 1. Green Light for Invoices uEarly notification n Applicant affirms it has confirmed with the vendor that services will begin in July, the first month of the funding year uServices have started uService provider notified via Form 486 Service Provider Notification Letter uInvoices flow (BEAR or SPIF)

5. 2. Technology Plans uCertification that relevant technology plans have been approved

6. Filing The Form 486 Key Tips 1. If filing early, be sure to check block 2, item6 2. Use correct entity number: no typos, no transpositions 3. Use correct FRN number: no typos, no transpositions

7. Form 500 Adjustment to Funding Commitment & Modification to Receipt of Service Confirmation uNew form dated April 2000

8. Purpose of Form 500 1. Change service start date n versus Form 471 n versus previously filed Form 486 2. Change contract expiration date n Why? uFCC year-end waivers may prompt this need uProjects extending into the funding year later than planned uProject is truncated

9. Purpose of Form 500 (contd.) 3. Cancel FRN n Why? uCancelled contract - vendor problems uPriority one project not feasible, due to insufficient funding for internal connections uDuplicate FRN mistakenly funded n Outcome uFunds released have a chance of being used for others

10. Purpose of Form 500 4. Reduce FRN n Why? uServices costs less than estimated n Outcome uFunds released have a chance of being used for others

11. Form 500 Notification Letters uService providers are notified of all changes uApplicants are notified only if there are funding commitment changes