Skip to main content



Month End is Month End!

In our legacy financial system, a full three days are allowed after the actual end of a month to post transactions to the previous month.  In KFS, the month-end time frame for posting data means, literally, just that—data must post by month end—i.e., by the very last day of the month—to be included in that [...]

Nightly Unavailability of KFS during Batch Jobs

Accounting transactions can be entered into KFS seven days a week, 365 days a year. Those transactions will be shown as “Pending Entries” in the application until the nightly batch jobs run and post the entries to the General Ledger (G/L). To keep the application and the G/L in sync, it will be necessary to [...]

“How ya doin’?”

As the project manager for the KFS at Cornell implementation, people curious about the project often stop me while I’m visiting offices around campus. Inevitably, I’m asked a variation of the question, “Sooo, how’s the project going? Are you really going to make the date of July 1, 2011?” As we wind down 2010, I’d [...]

“You have to be very careful if you don’t know where you’re going…

or you might not get there.” – Yogi Berra Yogi Berra may have known a thing or two about project management. Out of the KFS project’s business process analysis effort (Fit sessions), we are seeing clear pictures of how each of the KFS modules will be used and how the system must be configured. For [...]

Interface Analysis and Update Planning is Under Way

As we move from legacy financial applications to KFS, campus applications and services that interact with the central financial system must continue operating correctly. Making sure these interfaces are ready for KFS is a priority for the KFS Implementation technical team. During the last week of February, the KFS Interfaces team held several introductory meetings [...]

Archives