FreedomTaxed

I ran the ATX2013 admin console, and chose the "file settings" tab. The backup frequency is right there, and I set it to "Daily" instead of "Hourly". I've been deleting the excess saved database folders. The perils of our company's learning curve, I suppose.

I took a closer look and found ATX2013 was making a new backup of itself every hour, since 2014-12-06 (when we installed the new server), meaning it's made over 2800 copies of itself. I'm calling tech support to get this feature turned off.

Well, tech support doesn't know what I'm talking about, Jack. Here's what my D: drive on the server looks like: D:ATX D:EMPLOYEES D:SCANS The EMPLOYEES and SCANS folders are only 10-11 GB. ... I did an investigation just now and determined that the D:ATX2013BACKUPDATABASE folder is now 748GB. That's 3/4 of the entire drive. The darned thing is making an entire copy of its database every day or so. I'm going to call back and ask 'em how to turn that off.

Invariably my diet during tax season sucks. I have to resort to popping vitamin pills, since at the end of a 12hr day at the office, I look back and find that I ate: 1. Tea and cookies. Sugar in the tea, of course. 2. A burrito. 3. Some potato chips. 4. Soda. 5. Bottle of water. 6. Kit-Kat bar from the client bowl. For a time I was preparing salads by hand every day, then it just got too busy. Then when it slumped, I was out of the habit. At best I was sprinkling a bag of pre-cut greens over my burrito. I lose weight over the cold parts of the tax season since I expend quite a bit of energy keeping warm when I go home, after being on-the-go during the day.

We came in a few days ago and ATX 2014 wouldn't roll over. Then we noticed ATX 2011 said it had run out of disk space. "There's lots of space on that drive" I had thought. I checked and all the free space was gone. It's a 1 terabyte drive! The employee share was only 4GB, and the scans were about the same. ATX had filled up 996 GB. Clients were sitting there pissed, as I moved the ATX 1999 to ATX 2002 files off the server drive and set the trash bin to 10GB. At the end of these hurried actions I had 18GB free. Whew! Suddenly we could do things. I come in this morning, a scant 2 days later, and I'm down to 4GB free. What the heck is going on? I'm moving more ATX years onto another drive (I'm moving ATX 2003 now), but this is still a ridiculous amount of disk usage.

We hear SALY frequently for Schedule C. I've never run into the same thing for a W-2, but I haven't been at this long enough to make the claim well enough. Surprisingly, we don't get many "just use my last pay stub".

We started our search a little after Nov 1st. Our first interview was on the 5th. Official training started 3-4 weeks later. I don't think our timeline is at fault. What I'll try to fix next year is my failure to fix the business owner. I left all post-interview vetting efforts to her, and it's clear to me now that she pencil-whipped it all. I can't let that happen again. I also blame myself for letting all the little indicators go by me, when they clearly told me who was a severe problem just waiting for it's time to appear. The most troublesome employee today was the one who was falling asleep during training, for example. Next year's gotta be different, or I should just quit. There's no point in inviting cobras into your bed.

The previous business owner had always tried to hire people who didn't have tax prep experience at all. I'm starting to wonder if there was a method to that madness. There's at least the distinct possibility that they'll do what you order them to do, and your monopoly on knowledge gives your orders a natural authority.

Do you have a link to that? I'm going to need all my faculties and tools in order to wage a hiring war next year.

End result: It was a disaster. I can't wait for April 15th to kick these people out the door. I'm kicking myself daily for hiring them (note: I'm not the owner so I didn't have full control of the hiring process). Clarification: I was served up drama, lies, endless incompetence, refusal to obey or follow orders, and militant defensiveness when the least attempt was made to criticize or correct errors. The capper on the deal today was in FINALLY getting a response from the IRS about the alleged EA certification for one of our hires. I sent email to [email protected] to check on the person's EA; I gave the person's first and last name, and their address. The IRS page for this matter assured me that they had a policy of responding within 72 hours. I followed up two weeks later, and still no response. Finally, 38 freakin' days later, I get a response: "Based on the information provided, we have no record for this person." Translation: The employee lied about having an EA. The IRS being impossibly late in responding is one thing. If this is the standard response time, then it's impossible to vet in time an employee candidate when they claim to be an EA. But that's just the icing on a lot of dysfunctional cake. What the heck is out there in the land of tax preparers? It looks like legions of dramatic liars and prima donnas... people who are doing tax preparation work since they can't hold down a real job. The sad thing is that this year we paid $300 to register on monster.com to get qualified candidates. At first, that's what it looked like. Then a lot of little things kept arising during our training period, and then during the actual tax season, it's like people pulled off their fake skin-masks and revealed they were horned demons within. Do any of you run in firms, and so how do you search for and properly vet candidates? Are we pretty much doomed to get insane princesses since this is seasonal work? The two people we hired for part time work, who had real jobs during the day, gave us no problems whatsoever. They wanted to work in tax prep to get some experience in the field.

Anything we have that's older than our voluntary document-retention period (currently 6 years) is shredded or given back to the client where appropriate or convenient.

I can understand the IRS not divulging the information. The same laws that protect you and your tax return, protect anyone who files one, fraud or not. The key issue is, does the IRS do anything about the fraudster.

Is trading your wife in, a deductible event? Discuss it with the husband. {runs away}

IRS Pub 334, Chapter 8, outlines how to decide if an expense can be deducted from business revenue. In general, you can deduct "[r]epairs that keep your property in a normal efficient operating condition". But you also can't deduct "[p]ersonal, living, and family expenses". This is a gray area. You have to ultimately fall back upon the issue of not taking an unreasonable position. To wit, you know that adding a medical expense to the Schedule C is unreasonable, because an IRS auditor is likely to conclude that you can still talk and make an appearance in business, regardless of tooth damage.

TP training has nothing to do with anything, Gail, as I'm sure you know. The IRS refuses to put PTINs on hold at the efile level when algorithmic examination amply demonstrates that certain PTINs are producing a string of questionable returns; the held PTIN would automatically cause a rejection at the efile level, and that PTIN remains on hold until some sort of phone-based procedure is followed... like calling the IRS Office of Tax Preparers and having an IRS employee simply review a randomly selected questionable filing (previously accepted be efile) and giving the preparer a Pass/Fail rating. If the preparer satisfies the IRS employee that he can justify the return, then the preparer Passes and the hold is lifted. If the preparer Fails, then the hold remains, and the preparer has to go to an IRS office and essentially appeal the hold, which is a more thorough review of a randomly selected questionable filing, or two, and if that also Fails, then the PTIN is defunct for the rest of the year. Obviously this isn't too difficult to arrange, is "fault tolerant", and it highly motivates preparers to keep their noses clean or they'll lose the PTIN for the rest of the year. Since the supply of PTINs during tax season is limited, this should be a workable system.