This Finance Division Update email is for Business Managers, MOU Leads, ConnectCarolina Finance Liaisons, Finance Council, Finance TIPs, Finance Campus Working Groups and Finance Division staff. Please share with the ConnectCarolina Finance users in your school/division. We will send updates weekly and as needed.
- NEW! April Month-End Close Deadline: Journal entries, data collect batches and journal imports should be received by Accounting Services by close of business on Thursday, April 30.
- REMINDER! System Outage: ConnectCarolina will be unavailable on Sat., April 18, from 8 a.m. to 8 p.m. for maintenance. Please plan accordingly.
- Year-End Close Prep Course: There are multiple sessions of the course Preparing for Year-End Close: Reviewing Open Transactions will discuss how to identify open (unposted) transactions and either delete or process them, in preparation for year-end close. Refer to the ConnectCarolina training calendar for dates and times.
- Consolidated Info from Finance Updates: A table that consolidates information from all Finance daily/weekly updates is now online, organized by topic and searchable on the ccinfo website>Finance tab: http://ccinfo.unc.edu/finance/ .
Users are encouraged to call the Help Desk when they are unsure who to contact for issue resolution. While users may have worked with a specific consultant or BA for another issue, any new issues must be submitted via a remedy ticket, not by calling an individual directly. This is the fastest way to obtain assistance and allows the project team to be able to track issues to determine the scale of the impact to all users.
All technical questions should be directed to the Business Systems Help Desk at 919-962-HELP, or submitted via a help ticket online at help.unc.edu (select ConnectCarolina > ConnectCarolina Finance > the appropriate area of concern).
Functional or business process questions – plus any tips you have to offer – can be added to the ConnectCarolina user discussion forums.
Suggestions for content can be emailed to email@example.com.