Legacy vs. SFS: How to determine which process, forms, and coding to use by type of transaction.

Use Legacy Codes	Use SFS Codes
Input form using old coding. This would include use of the following forms: Cash Advances Travel Advances Receipt/Sales Credit Deposit Forms Receipt/Sales Credit Transfer Forms Salary payment transfer (Legacy coding)	Input form using New (SFS) coding: Cost Transfer Request (Non Salary) Direct Payment/Employee Reimbursement Form External Requisition Form – complete form through My UW on the Services tab Inter Departmental Billing Internal Work Order – complete form through My UW on the Services tab Payment to Individual Reports Purchasing Card PVS Net entries (default coding and edits) Refunds of receipts/sales credits Salary Cost Transfer (SFS coding) Travel Expense Reports Vendor Refunds
On-line Accounting activities: BUDT	On-line activities: WISDM Salary encumbrance web application Salary payment transfer (done centrally online) SFS Add-on Tools Transactions Across Fiscal Years (TAFY) Reconciliation Outlyers Report
On-line non-Accounting activities: ESIA IADS & payroll transactions	WISDM subscription reports
Use of the following Data Views: UDDS_Name	Use of the following Data Views: Detail Accounting Transactions Summarized Accounting Data ESIS Award Accounting Prior Year Fund Balance Detail Payroll Transactions Detail GL & Payroll Transactions ESIS Chartfield Summary

Use Legacy Codes

Use SFS Codes

Input form using old coding.
This would include use of the following forms:

Input form using New (SFS) coding:

On-line Accounting activities:

On-line activities:

On-line non-Accounting activities:

WISDM subscription reports

Use of the following Data Views:

Use of the following Data Views:

See more information about coding information: http://www.bussvc.wisc.edu/acct/coding.html.

University of Wisconsin-Madison