Gap Analysis / Requirements Gathering  The goal of this meeting is to gain a mutual understanding of the identified remediation gap and to document any requirements necessary for the remediation of that gap.  For example, if there is a reporting gap, we would identify what information is needed (specific data elements to include) to bridge that gap and how that information needs to be retrieved (reporting frequency, parameters).

• General Ledger

1. From College Critical Issues
   1. Fund Balancing and Accounting
      1. Report/Query Development
         1. Summary data (by Account, Fund) of what is in a module sub-ledger to be posted to the General Ledger
         2. Error reports for Journal Generated data
            1. What module sub-ledger transactions didn’t get sent to the General Ledger
            2. What generated Journals are now in an Error status
      2. Training/Documentation Development
         1. QRGs/Video for processes being performed by the colleges
            1. Make sure “gotchas” are identified as part of these process-specific documents
            2. Needed for Journal Generation processes
            3. Needed for Journal Entry
            4. Needed for Journal Upload
            5. Needed for Journal Maintenance processes
               1. Journal Edits
               2. Posting Journals
               3. Unposting Journals
         2. Functional documentation around how our interface processes work and the affect any CEMLIs have on those processes
            1. Payroll to GL interface
            2. CS to GL Interface, including Student Financials and Financial Aid transactions
      3. Other Discussion Notes
         1. Accounting Process Question for State Board
            1. We are currently balancing on all Chartfield segments
            2. Is this something that could be changed, or are there other requirements that are driving this process?
               1. The increased number of lines involved makes reconciliation and reclassification more difficult
         2. Need documentation on the Overnight Job Schedule
            1. Would help people understand what jobs are being run overnight so they know what needs to run during the day
            2. This item was escalated out of the individual pillar discussions since it affects all areas; we won’t be addressing it in our Finance-specific sessions
         3. Need to examine revenue recognition in the end-to-end Billing process
            1. This topic is part of a separate “Billing Accounting Processes” WebEx we will have later in the remediation process
         4. Need more information as it relates to cash reconciliation
            1. This topic is part of a separate “GL Integration and Reconciliation” WebEx we will have later in the remediation process
   2. Year-End Close
      1. Training/Documentation Development
         1. Documentation on year-end and/or post-year-end close correction process for individual modules
            1. Overall correction process documentation
            2. Task specific QRG/Video training content
         2. Document that outlines the different parts of year-end closing and who is responsible for what
            1. Overall year-end process documentation, for example
               1. How are Closing Rules updated?
               2. Who runs year-end close processes?
               3. What happens when the processes are run?
               4. How/when are accounting periods opened and closed?
            2. Task specific QRG/Video training content
      2. Other Discussion Notes
         1. System Process Question for State Board
            1. We are currently closing individual module sub-ledgers prior to closing the GL for adjusting entries
            2. Is it possible to keep modules open later?
            3. If not, need standard processes and documentation for getting corrections into module sub-ledgers
         2. System Process Question for ctcLink Project Team
            1. Legacy has the Close/Open process; does similar functionality exist within PeopleSoft?
            2. College were able to set where certain Accounting segment values (e.g. Departments) were closed to at year end
            3. Answer: PeopleSoft “Closing Rules” provide the same functionality that the Legacy Close/Open process did; how the colleges provide information as it relates to these Closing Rules will be part of our year-end documentation
   3. Inter-/Intra-Agency Transactions
      1. AFRS Reporting needs as they relate to Inter-Agency transactions
         1. When invoicing or billing, need to be able to code that payment in order to identify due-to/due-from other agency
            1. Suppliers
            2. Customers
         2. Student Financials also has due-to/due-from that need to be addressed
            1. External Organizations
      2. Report/Query Development
         1. Need to be able to see due-to/due-from by Agency at a given time
            1. Summary balance by Agency, by Account, by Fund
   4. Unclaimed Property
      1. Documentation/Training Development
         1. Need overall process document for unclaimed property
            1. There are QRGs for stale dating a check, but it does not explain what is happening in the system when this is done (e.g. are accounting entries triggered by this?)
            2. There are QRGs for canceling/re-issuing a check, but it’s unclear if this can/should be done for stale dated checks
            3. There are QRGs for the escheatment process, but it’s unclear how/where this fits into the larger picture of processing unclaimed property
2. From Open Remediation Tickets
   1. Inter-Fund Transactions
      1. Documentation/Training Development
         1. Would be helpful to have documentation that explains Fund roll-ups for those new to the system

1. Discussion on revenue recognition in the end-to-end Billing process  will be covered in a separate “Billing Accounting Processes” WebEx we will have later in the remediation process
2. Discussion on cash reconciliation will be covered in a separate “GL Integration and Reconciliation” WebEx we will have later in the remediation process

• n/a