This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n7http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
revhttp://purl.org/stuff/rev#
n4http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n6http://data.yelp.com/User/id/

Statements

Subject Item
n2:lnFhwXz78tEPGamhUmLiAQ
rdf:type
rev:Review
schema:dateCreated
2013-04-15T00:00:00
schema:itemReviewed
n4:3eX71PVVooLwKJWtckqF1g
n7:funnyReviews
0
rev:rating
1
n7:usefulReviews
4
rev:text
We have been using the Payroll company for a few months now and I am pretty unimpressed. It seems that their control systems could use a lot of work. Our problem stems from the fact that we changed our company's banking to a new bank. This should not cause any problem right? Companies do it all the time right? You would think this as I, of course, notified them of the change three months ago. I sent in a form and a voided check from the new account. . But despite going through the process of doing all that. And despite the fact that they have pulled payroll from the new account. This past payroll they tried to pull the funds from the old account. When they got the NSF response they sent me a nasty-gram about the right to charge a $150 penalty. I alerted them to the fact that they might be trying the old account and gave them the last four digits of the new account. I also verified that there was amble funds to cover the payroll. Today I notice that they have pulled the payroll from our new bank account, twice. Now we are over drawn. I alerted them to the error and got a stock email reply with a case number. When I had heard nothing more after a couple hours I called. I was told that, "Someone will get back to me later today." When you pull thousands of dollars out of someone's account mistakenly, I think you should have a better answer than, "later today." I think moving our payroll to these guys was a mistake.
n7:coolReviews
0
rev:reviewer
n6:8ImtNeMLW8Io21oCHcY0KQ