<?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>Staffing Software&#187; Time Cards</title>
	<atom:link href="http://blog.tempworks.com/tag/time-cards/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tempworks.com</link>
	<description>Staffing Software Notes from TempWorks</description>
	<lastBuildDate>Mon, 17 Jun 2013 06:34:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Difficult Problem, Simple Solution</title>
		<link>http://blog.tempworks.com/success-stories/difficult-problem-simple-solution/</link>
		<comments>http://blog.tempworks.com/success-stories/difficult-problem-simple-solution/#comments</comments>
		<pubDate>Wed, 04 May 2011 20:19:45 +0000</pubDate>
		<dc:creator>TempWorks Software</dc:creator>
				<category><![CDATA[Success Stories]]></category>
		<category><![CDATA[Ali Panjwani]]></category>
		<category><![CDATA[Customer Support]]></category>
		<category><![CDATA[Time Cards]]></category>

		<guid isPermaLink="false">http://blog.tempworks.com/?p=633</guid>
		<description><![CDATA[One of the difficulties in running a full-service staffing firm is dealing with the many ways that time card data can get to you. It’s no longer just a simple drop of a paper time card through the mail slot.&#160; Today, there’s integrated time clocks, time clock data feeds, web service feeds, online web portal time entry, faxed time cards, paper time cards, electronic document cards, group time cards, time &#8230;<p style="float:left; font-weight:bold;">Continue reading: <a class="read_more" href="http://blog.tempworks.com/success-stories/difficult-problem-simple-solution/" title="Difficult Problem, Simple Solution">Difficult Problem, Simple Solution &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>One of the difficulties in running a full-service staffing firm is dealing with the many ways that time card data can get to you.</p>
<p>It’s no longer just a simple drop of a paper time card through the mail slot.&nbsp; Today, there’s integrated time clocks, time clock data feeds, web service feeds, online web portal time entry, faxed time cards, paper time cards, electronic document cards, group time cards, time cards spanning multiple pay periods and more.&nbsp; You name it, and our clients do it.</p>
<p>That flexibility allows them to succeed where their competitors can not.&nbsp; It also can create hectic moments in payroll.&nbsp; For example, a payroll processor can get confused organizing so many time card types.&nbsp; Nevertheless the paychecks need to get out – fast.&nbsp; To make sure that happens, TempWorks takes pride in providing a first-class team of technology and staffing professionals on our support desk.</p>
<p>Take support specialist Ali Panjwani, for example.&nbsp;&nbsp; A client called Ali on Monday, stressed about an error she was encountering while trying to push time entries through to payroll.&nbsp; Ali had the client send him a screen shot, and he quickly identified the problem.&nbsp; After some further digging he devised a solution, a quick update by him that would save the client hours of work.&nbsp; Problem solved.</p>
<p>Ali, an Accounting and MIS major at Winona State, said he often deals with similar payroll issues, each one with a slightly different solution.</p>
<p>“I’ve been fascinated by software since high school,” says Ali.&nbsp; “But working at TempWorks has opened my eyes about the outside world, and now I go back to college with a purpose.”</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tempworks.com/success-stories/difficult-problem-simple-solution/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
