140 likes | 319 Views
Chart of Accounts Team. Al Roberson Ben Martin Van Adams Carol Rylee Jeff Quirico. Chart of Accts Committee. Formed in July, 1999 (Amy Taylor, Chair) Hired consultant from KPMG Reviewed PeopleSoft Chart structure Convened Focus Groups (180 users - 95 departments) Final Report May, 2000.
E N D
Chart of Accounts Team • Al Roberson • Ben Martin • Van Adams • Carol Rylee • Jeff Quirico
Chart of Accts Committee • Formed in July, 1999 (Amy Taylor, Chair) • Hired consultant from KPMG • Reviewed PeopleSoft Chart structure • Convened Focus Groups (180 users - 95 departments) • Final Report May, 2000
PeopleSoft Chartfields • Business Unit - 5 characters • PS Fund - 5 characters • PS Account - 6 characters (soon to be 10) • PS Department - 10 characters • PS Program - 5 characters • PS Project - 15 characters • PS Class - 5 characters
UD Logic for Chartfields • Use of Speed Types • Considered Reporting Needs • Importance of Visual Identification • Use of ranges for trees maintenance • Drop Down Boxes
PS Fund • Roughly equivalent to current 1-9 funds • OPBAS • OPSS • OPBAL • NOEND • NOPLT • NOLOA • AGNCY
PS Account • Roughly equivalent to object codes • 8xx category will be replaced by 4xx items • Required Chartfield for a transaction (not populated by speed type) • Assets & Liabilities • May be fully defined by this field • Can replace current 14-digit code
PS Account • Examples: • A Revenue – 046 = R04600 • A Salary – 202001 = 1PFAAA • A Support Item – 410 = 141000 • An Asset – 01813000000220 = A1CWT1 • A Liability – 01934000000200 = L3BCBS • A Fund – 01786000104 = FGNRSV
PS Department • Equivalent to current UD 11-digit code (excludes Asset & Liabilities) • 1st 4 characters identify major unit (matches Registrar’s acronyms) • Next 2 characters generally identify current fund type • Final 4 characters randomly assigned • PS Department = Speed Type
PS Program • Equivalent to UD Expense Function • Will not include Transfers & Allocations • No Revenue source – will be identified by PS Account
PS Project • Key field for integration into project module • Used for further identification for construction projects & contracts & grants • Subject to change as learn about grants module • Will not need project-to-date designation
PS Class • User-Defined field • Pre-set definitions to be maintained centrally (For example: User Field 1) • Departments will maintain specific values in separate location in department • For multiple use and specific programs, individual definitions may be considered for official PS Class
Chartfield Conversion • Table will be used as initial system conversion tool, and • UD Crosswalk Tool for users • Old to New codes • New to Old codes later • Web-Based tool
Issues addressed http://www.udel.edu/UDFS/code-conver-questions.htm http://www.udel.edu/UDFS/Decisions-made.htm
Input from Teams • Need input from Teams • ASAP or no later than January 31 • Will accommodate suggestions where possible • Will suggest alternative solutions where appropriate