Every accountant I talk to has had some version of the same late-night thought. It usually shows up around the third week of March, somewhere near account 47 of 80.
"Is this thing coming for my job?"
Short answer: no. Longer answer: the part of your job it can actually do is the part you would happily pay someone else to do anyway. And if you have ever spent a Tuesday evening typing a client's trial balance into tax software one line at a time, you already know exactly which part I mean.
Let me explain what AI is genuinely good at, what it is genuinely bad at, and why the gap between those two things lands almost perfectly on the worst hour of your tax prep workflow.
AI is a classifier. That is the whole trick.
Strip away the hype and most of what these tools do well comes down to one skill: looking at something messy and telling you what category it belongs to.
That sounds unimpressive until you remember what a client trial balance looks like.
You get a file. The bookkeeper called an account "1010 Op Cash - WF Main." Another one says "Ck Acct (old)." There is something named "Misc Exp - ASK JIM." One client capitalizes everything, the next one uses all lowercase, and a third one puts account numbers in front with a little dot separator that changes every year depending on which version of QuickBooks they exported from.
None of that is standardized. There is no chart of accounts authority making everyone name things the same way. Every client is a small dialect of accounting English, invented by whoever set up the file, and you have to translate all of it onto a standardized tax return.
That is a classification problem. It is messy input, fixed output, and enormous variation in how humans express the same idea.
Which happens to be the single thing machines have gotten very, very good at in the last few years.
What it cannot do, and this is the important part
Here is the line, and it matters more than anything else in this article.
A tool can recognize that "Meals - Client Development" is a meals account. That is pattern matching, and it is reliable.
It cannot decide whether the 50 percent disallowance on those meals belongs in the client's books or belongs on Schedule M-1 as a book to tax difference. That is not pattern matching. That is understanding that the client's financial statements need to stay correct while taxable income goes somewhere else, and knowing which one your client's banker is going to read in May.
It does not know the client bought a building in October and never mentioned it.
It does not know that the "Loan from Shareholder" account is actually three years of undocumented draws that someone needs to have an uncomfortable conversation about.
It does not know that this partnership has a special allocation buried on page 14 of an operating agreement nobody has opened since 2019.
And it cannot sign the return. You sign the return. You carry the liability, your license is on the line, and no serious tool should ever ask you to accept something you have not looked at.
So the division of labor is not subtle. The tool handles recognition. You handle judgment. Recognition is the tedious part. Judgment is the part clients actually pay you for.
The mistake nobody talks about: keying
Ask a preparer what goes wrong in tax prep and they will tell you about complicated things. Basis. Section 754. Allocations.
In practice, a shocking number of problems are simpler and dumber than that. Somebody typed a number wrong.
You have a trial balance open on one monitor and tax software on the other. You read a figure, you turn your head, you type it in. Then you do that eighty more times. Somewhere in there you type 12,450 instead of 12,540, because your eyes did the thing eyes do at 9pm.
That error has two nasty properties.
It is silent. The return still calculates. Nothing turns red. No diagnostic fires, because there is nothing internally inconsistent about a wrong number sitting on a correct line.
And it is invisible on review. A reviewer looking at that return sees a plausible advertising figure on the advertising line. To catch it they would have to go back to the trial balance and tie every number, which is the exact work you just did and nobody wants to do twice.
Here is the part that should bother you. The numbers already exist in a file. They came out of an accounting system, correctly, in digital form. And then a human being retyped them into a different system. Every single one of those keystrokes is a chance to introduce an error that did not exist thirty seconds earlier.
We do this because that is how it has always worked, not because it makes any sense.
Where Ledger IQ actually helps
So that is the setup. Here is what we built and, more importantly, why each piece is the way it is.
It suggests. You confirm. Always.
When you upload a trial balance, Ledger IQ proposes a mapping for each account. Those are suggestions and they are visibly marked as suggestions. You accept them or you reject them.
You cannot export a tax import file while suggestions are still sitting there unreviewed. The software will stop you and tell you how many are pending. That is deliberate and we are not going to remove it. An unreviewed mapping is an opinion, and opinions do not belong on a filed return.
It can only choose from lines that actually exist on your return.
This is the piece I would want to know about if I were evaluating a tool like this, because it is where a lot of AI products quietly fall over.
Ledger IQ picks from the real line items on the form you are filing. Not from a general idea of what a tax return looks like. It cannot propose a category that does not exist, it cannot invent a plausible sounding line, and it cannot put a number somewhere the form does not have a slot for. The worst case is that it declines to guess and leaves an account for you to handle, which is exactly the behavior you want. A missing suggestion costs you fifteen seconds. A confidently wrong one costs you a lot more.
It tells you why.
Every suggestion comes with its reasoning. Sometimes it is "this name matched accounts receivable." Sometimes it is "you mapped this same account name last year." You are reviewing a recommendation with a stated basis, not accepting a black box.
It remembers your decisions.
Map "Misc Exp - ASK JIM" once and the software remembers where you put it. Next year the same client comes back and that account arrives already handled. The year after that, more of the file is already done.
This compounds in a way that surprises people. Your first return in a new tool is roughly a wash on time. Your second is meaningfully faster. By the third year you are reviewing decisions your past self already made instead of making them again from scratch. And if a different preparer in your firm picks up that client, they inherit your reasoning rather than reconstructing it from a finished return.
The numbers move. Nobody retypes them.
This is the quiet one, and it might be the most valuable thing on this list.
The balance from the client's file flows through the mapping and into the tax software import file. It is the same number the whole way. There is no point in that chain where a person reads a figure and types it somewhere else.
You cannot transpose a digit you never typed.
And everything has to foot before it leaves.
The Working Trial Balance shows unadjusted, adjustments, adjusted, and tax balances side by side, with totals proving each column ties. The income proof walks net income per books through your book to tax differences down to ordinary business income, which is the number that should land on page 1 and in Box 1 of every K-1.
If that does not tie, you find out on your workpaper, on your schedule, at your desk. Not from a notice in fourteen months.
The honest pitch
AI is not going to prepare the return. It is not going to have the conversation with the client about reasonable compensation, or notice that the balance sheet has been quietly wrong since 2021, or decide how aggressive to be on a position.
What it will do is take the eighty line translation exercise that stands between you and the actual work, and turn it into a review instead of a data entry session.
That is not a threat to your practice. That is somebody finally showing up to do the filing.
Ledger IQ supports Forms 1065, 1120S and 1120, with exports for Drake, Lacerte and UltraTax CS. It is free during early access, so you can try it at portal.ledgeriq.ai on a real client file without a credit card and decide for yourself.