<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wesleyan Financial System Implementation</title>
	<atom:link href="http://wfs.blogs.wesleyan.edu/feed/" rel="self" type="application/rss+xml" />
	<link>http://wfs.blogs.wesleyan.edu</link>
	<description>Just another blogs.wesleyan.edu weblog</description>
	<lastBuildDate>Thu, 18 Jun 2009 13:45:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>AP Voucher and Purchase Order Tips</title>
		<link>http://wfs.blogs.wesleyan.edu/2009/06/14/ap-voucher-and-purchase-order-tips/</link>
		<comments>http://wfs.blogs.wesleyan.edu/2009/06/14/ap-voucher-and-purchase-order-tips/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 18:35:18 +0000</pubDate>
		<dc:creator>ebelow</dc:creator>
				<category><![CDATA[Documentation]]></category>

		<guid isPermaLink="false">http://wfs.blogs.wesleyan.edu/?p=90</guid>
		<description><![CDATA[Purchase Order Tip Sheet
To Route a Purchase Order to Olga Bookas, Purchasing Manager

If you do not know what vendor you want, enter &#8220;req&#8221; in the vendor field and click the small magnifying glass.  This will return a vendor called REQUISITIO-001 (vendor number 9999999999).  Select this vendor.  You can enter yourself as the buyer.
If you know [...]]]></description>
			<content:encoded><![CDATA[<h1>Purchase Order Tip Sheet</h1>
<p><strong><span style="text-decoration: underline">To Route a Purchase Order to Olga Bookas, Purchasing Manager</span></strong></p>
<ol type="1">
<li>If you do not know what vendor you want, enter &#8220;req&#8221; in the vendor field and click the small magnifying glass.  This will return a vendor called REQUISITIO-001 (vendor number 9999999999).  Select this vendor.  You can enter yourself as the buyer.</li>
<li>If you know the vendor, select the correct vendor, but select OBOOKAS as the buyer.  This will route the PO to her to review and negotiate a good price.</li>
<li>Regardless of which method you use to route a PO to Olga, be sure to enter a full description of what you want in the Comment Section.</li>
</ol>
<p><strong><span style="text-decoration: underline">To Change or Select a Billing Location or Ship-To location</span></strong></p>
<ol type="1">
<li>The Billing Location always defaults to the Accounts Payable campus address</li>
<li>The Ship-To location always defaults to the campus address of the Buyer</li>
<li>To look-up a different address for either, click the magnifying glass
<ol type="a">
<li>Enter &#8220;W_xxx&#8221; to find a Wesleyan campus address</li>
<li>Enter &#8220;F_xxx&#8221; to find a facilities address (this is a list of all buildings)</li>
<li>Enter &#8220;S_xxx&#8221; to find a Shipping address that has been setup for your department.</li>
<li>You can enter partial codes, click the search and get all values that begin with those letters.</li>
</ol>
</li>
</ol>
<p><strong><span style="text-decoration: underline">Line Information</span></strong></p>
<ol type="1">
<li>If you want to use the P.O. to list a specific quantity of items you are buying, enter a description, quantity, Unit of Measure (UOM) and amount <span style="text-decoration: underline">per item</span>.  When you tab out of the Amount field, the total will be calculated (quantity X amount). </li>
<li>If you are just buying a Service, or something for a flat rate, check the &#8220;Amount Only&#8221; box on the far right.  Be sure to change the Category to &#8220;Service&#8221;.  The UOM must still be entered. </li>
</ol>
<p><strong><span style="text-decoration: underline">Distributions</span></strong></p>
<ol type="1">
<li>A Smartkey and Amount is required even if you do not know who the vendor will be or if Olga is going to get bids for you.  Olga will change the amount before the P.O. is final.</li>
<li>Budget Checking must be performed before Submitting to Workflow.</li>
<li>Multiple distribution lines can be entered with different Smartkeys or different Accounts, but they must all add up to the total in the Line Information.</li>
</ol>
<p><strong><span style="text-decoration: underline">Dispatching a Purchase Order</span></strong></p>
<ol type="1">
<li>Once a P.O. has been approved, it must be dispatched by clicking the button at the top of the P.O. page.</li>
<li>A P.O. <span style="text-decoration: underline">MUST</span> be dispatched in order to copy the P.O. information onto and A.P. Voucher.</li>
<li>The dispatch method selected is strictly informational so you know how it was dispatched, except for the E-Mail method.  If E-Mail is selected the P.O. will be e-mailed to the vendor if an e-mail address has been entered on the Vendor profile.</li>
</ol>
<p> </p>
<p><strong><span style="text-decoration: underline"> </span></strong></p>
<p><strong><span style="text-decoration: underline"> </span></strong></p>
<h1>AP Voucher Tip Sheet</h1>
<p><strong><span style="text-decoration: underline">A Vendor is Required on All Purchase Orders and Vouchers</span></strong><strong></strong></p>
<ol type="1">
<li>If you are sending the P.O. to Olga to find a vendor, use REQUISITIO-001</li>
<li>If you cannot find the vendor in the lookup, complete the New Vendor Request Form and send to the Accounts Payable Office.  They will notify you when the vendor has been entered.  This includes payments to individuals.</li>
</ol>
<p><strong><span style="text-decoration: underline">Invoice Number</span></strong></p>
<ol type="1">
<li>An invoice number is required for all vouchers.  Every voucher must have a unique invoice number for that vendor.</li>
<li>If you are entering a voucher without an invoice number, follow the guidelines for Invoice Numbering prepared by the AP Office (on the Finance web site).</li>
</ol>
<p><strong><span style="text-decoration: underline">Documentation and Attachments</span></strong></p>
<ol type="1">
<li>The invoice or other documentation must be attached to the Voucher.</li>
<li>Instructions for scanning using your office copier can be found on the WFS Blog and the Finance web site.  Call ITS Desktop support if you need additional assistance.</li>
<li>Departments must keep original invoices and documents according to retention policy</li>
</ol>
<p><strong><span style="text-decoration: underline">Travel Expense Vouchers</span></strong></p>
<ol type="1">
<li>If the traveler has a Wesleyan purchasing card, most expenses should be charged to the card.  P-Card holders should attend the training session on P-Card re-allocation.</li>
<li>The traveler can use the old paper form and scan it to attach to the Smart Doc Voucher.  The correct chart fields must be entered on the Smart Doc Voucher.</li>
<li>A spreadsheet template will be available in early July that will also allow the traveler to itemize expenses.</li>
<li>All receipts must be scanned, along with the spreadsheet or paper travel form, and attached.</li>
<li>If the request is only for mileage, the details can be entered in the &#8220;Instruction for AP&#8221; section.   (Total miles, purpose and date of travel and rate per mile.)</li>
</ol>
<p><strong><span style="text-decoration: underline">Copying Details from a P.O.</span></strong></p>
<ol type="1">
<li>A P.O. will appear in the look-up only if it has been dispatched.</li>
<li>Select the P.O. and click &#8220;Copy PO&#8221; button</li>
<li>The dollar amount can be modified if the invoice is a different amount than the P.O.</li>
<li>The Invoice Number must be entered</li>
</ol>
<p><strong><span style="text-decoration: underline">Payment Methods</span></strong></p>
<ol type="1">
<li>To corporate vendors: All vendors are being asked to supply information so payments can be made electronically (EFT).</li>
<li>To Wesleyan employees:  Reimbursements will be made electronically using the banking information used for payroll.</li>
<li>To other individuals: Checks will be cut, unless the individual provides direct deposit information</li>
<li>For Petty Cash payments: An staff member requesting Petty Cash should request that a check be written using the AP Comment section.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://wfs.blogs.wesleyan.edu/2009/06/14/ap-voucher-and-purchase-order-tips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Invoice Numbering Conventions</title>
		<link>http://wfs.blogs.wesleyan.edu/2009/06/14/invoice-numbering-conventions/</link>
		<comments>http://wfs.blogs.wesleyan.edu/2009/06/14/invoice-numbering-conventions/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 18:32:03 +0000</pubDate>
		<dc:creator>ebelow</dc:creator>
				<category><![CDATA[Documentation]]></category>

		<guid isPermaLink="false">http://wfs.blogs.wesleyan.edu/?p=83</guid>
		<description><![CDATA[Invoice Numbering Conventions 
Every voucher must have a unique invoice number for that vendor.  In PeopleSoft; invoice number can be up to 30 characters.

Any alpha characters in an invoice ID must be entered in upper case.

Example, if the vendor invoice number is ab1234; it should be entered as AB1234.

When processing a voucher for a vendor [...]]]></description>
			<content:encoded><![CDATA[<p align="center"><strong>Invoice Numbering Conventions </strong></p>
<p align="center">Every voucher must have a unique invoice number for that vendor.  In PeopleSoft; invoice number can be up to 30 characters.</p>
<ul>
<li>Any alpha characters in an invoice ID must be entered in upper case.</li>
</ul>
<p>Example, if the vendor invoice number is ab1234; it should be entered as AB1234.</p>
<ul>
<li>When processing <strong>a voucher for a vendor that has an invoice number</strong>.</li>
</ul>
<p>You will use the invoice number listed from vendor but without any spaces or punctuation.</p>
<p>Example, if a vendor invoice number is either 123 45 678, 123-45-678 or 123/45/678; it would be entered as 12345678, no spaces or punctuation.</p>
<ul>
<li>When processing <strong>a voucher for a vendor that</strong> <strong>does not</strong> <strong>have an invoice number</strong>.</li>
</ul>
<p> You will use the four digit department number from within the Smartkey followed by the invoice date formatted as MMDDYY.</p>
<p>Example, Smartkey 1001095100 would be entered with an invoice number 1095MMDDYY. Do not enter any spaces or dashes and numeric only.</p>
<p>If you get a duplicate error message on save using this format, research the invoice and if it is not a true duplicate add an alpha character on the end and make a note of the error on smart voucher under instruction to AP.</p>
<ul>
<li>When processing <strong>a voucher for a vendor that</strong> <strong>uses the same invoice number</strong> every month.</li>
</ul>
<p>You will use the invoice number from vendor, no spaces or punctuation, followed by the invoice date formatted as MMDDYY.</p>
<p>Example, vendor invoice 12-34-5 would be entered as 12345MMDDYY.<em></em></p>
<p>If you get a duplicate error message on save using this format, research the invoice and if it is not a true duplicate add an alpha character on the end and make a note of the error on smart voucher under instruction to AP.</p>
<ul>
<li>When processing <strong>a credit voucher</strong>, make sure to follow the procedure that fits above and add CM after the entry date to specify a credit memo. <em></em></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://wfs.blogs.wesleyan.edu/2009/06/14/invoice-numbering-conventions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Chart of Accounts</title>
		<link>http://wfs.blogs.wesleyan.edu/2008/07/24/team-2s-latest-news/</link>
		<comments>http://wfs.blogs.wesleyan.edu/2008/07/24/team-2s-latest-news/#comments</comments>
		<pubDate>Thu, 24 Jul 2008 21:51:49 +0000</pubDate>
		<dc:creator>ebelow</dc:creator>
				<category><![CDATA[Chart of Accounts]]></category>

		<guid isPermaLink="false">http://wfs.blogs.wesleyan.edu/?p=6</guid>
		<description><![CDATA[The most basic building block of the new financial system is an new chart of accounts.  PeopleSoft offers much greater flexibility in setting up a chart of accounts by providing a number of fields that can be used for different purposes to describe the "bucket" for expenses, revenue, budget, etc.  The terminology used in PeopleSoft is also different from what we are all acustom to in FRS, but more on that later.  Just remember that we will all need to learn some new terms.  The General Ledger Team has spent over two months discussing various scenarios for a new chart of accounts.  View the Power Point presentation linked at the bottom of this page to view the details of the current thinking. ]]></description>
			<content:encoded><![CDATA[<p>The most basic building block of the new financial system is an new chart of accounts.  PeopleSoft offers much greater flexibility in setting up a chart of accounts by providing a number of fields that can be used for different purposes to describe the &#8220;bucket&#8221; for expenses, revenue, budget, etc.  The terminology used in PeopleSoft is also different from what we are all acustom to in FRS, but more on that later.  Just remember that we will all need to learn some new terms.  The General Ledger Team has spent over two months discussing various scenarios for a new chart of accounts.  View the Power Point presentation linked at the bottom of this page to view the details of the current thinking. </p>
<h2>Converting FRS Accounts to new PeopleSoft Chart Strings</h2>
<p>A new PeopleSoft Chart String will be created for each FRS account number that has been used in the last three fiscal years (FY 2009, 2008 and 2007).  There will be a one-to-one relationship between the FRS account and the PeopleSoft Chart String.  Each department will be notified of their new chart strings sometime next spring.</p>
<p>The data (in other words, the revenue and expense detail) will only be converted in an aggregate manner.  The balance for each account at the end of each of the last three fiscal years will be converted into PeopleSoft, but not the individual transactional detail.  Users will still have the Financial Data Warehouse (Inquiry) to look up detail transaction.</p>
<p>The system will be live on July 1, 2009 and that will be the day that the new chart strings will be used.</p>
<p>To view the Power Point that explains our current plan of the new chart fields, click here:  <a href="https://wesfiles.wesleyan.edu:443/campus%20committees/WFS%20Implementation/Public%20WFS%20Documents/Chart%20of%20accounts.ppt">Chart of Accounts Power Point</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wfs.blogs.wesleyan.edu/2008/07/24/team-2s-latest-news/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
