Lacerte AI Automation: What Works, What Does Not, and Why

What Lacerte already does. More than most firms use. The Link client portal handles requesting and exchanging client documentation. e-Organizer collects information. Tax Scan and Import performs automated data extraction from scanned source documents. Financial Institution Download pulls data directly from financial institutions and payroll providers. SmartVault or the Document Management System holds the result. If your firm is doing manual data entry off a paper 1099 in 2026, the problem is adoption, not software, and no AI layer fixes that.

What the mature third-party market already does. Scan-and-populate is a solved, competitive category with Lacerte support. SurePrep's 1040SCAN extracts from source documents and exports into Lacerte, UltraTax, CCH Axcess and GoSystem. GruntWorx pushes extracted data straight into the return without an intermediate spreadsheet. Newer entrants such as Juno claim to cover 100-plus document types and to write into Lacerte's input screens across desktop, Rightworks, Verito and AWS-hosted installs. You should buy in this category, not build in it.

What is genuinely left. Extraction is a commodity. Expectation is not. No product knows that this particular client has had a rental in Vermont since 2019, sold half of it in the year in question, and always sends the closing statement late and buried inside a scan of eleven unrelated pages. The unsolved layer is a per-client expected-document set, derived from the prior-year return and last year's actual intake rather than from a generic organizer template, plus a classifier that files an inbound scan against that set and reports what is genuinely missing rather than what is merely not yet ticked.

The ceiling. A classifier is never right every time, and whatever it gets wrong needs somewhere to go, which is a human queue with a two-click override. Build the queue on day one. Firms that skip it end up with a silent misfile problem they discover in June.

What Lacerte already does. Lacerte handles K-1s the firm itself produces, well. The K-1 export moves Schedule K-1 data between returns, and the program reads Partner Information Type of Entity to decide which module a given partner's K-1 transfers to: Individual, Partnership, Corporate, S-Corporation or Fiduciary. If you prepare the 1065 and the partner 1040s, that is a solved path and you should be using it.

Where April actually hurts. Inbound K-1s from entities you do not prepare. A single 1040 with eleven of them, arriving between March 20 and September, as PDFs with no layout consistency, each carrying a stack of attached statements: the line 20 codes on a partnership K-1, the line 17 codes on an S-corp K-1, state apportionment schedules, section 199A information, and a footnote page written in prose that changes the answer. Lacerte's own export path cannot help you here, because the data never originated in your Lacerte.

What AI is genuinely good at here. Two things. First, extraction of the boxed numbers, which is now reliable enough that specialist K-1 extraction is its own product category. Second, and more valuable, reading the attached statements and surfacing the sentences that a preparer would otherwise find on page seven at eleven at night. A model that returns "this K-1's footnote reports foreign taxes paid to two jurisdictions and a section 743(b) adjustment, neither of which appears in the boxed figures" earns its keep, because it is doing retrieval and summarisation, which is the thing it is actually good at.

The ceiling, and it is a hard one. Basis. At-risk. Passive activity grouping. Whether the 199A information is usable as presented. None of that is extraction, all of it is judgment against facts that often are not on the document at all, and none of it should be automated. The honest design puts the model on the reading and the flagging, and puts the preparer on the decision, with the model's output attached to the workpaper as evidence rather than as an answer.

What Lacerte already does. Diagnostics, and a lot of them. Lacerte's diagnostics catch the things that are wrong against the form instructions. They do not catch the things that are wrong against your firm.

The gap, stated precisely. Every firm has a senior reviewer whose value is a checklist that exists mostly in their head. A state that should have been added because the client mentioned a move in a phone call last August. An account balance that swung past whatever threshold your firm treats as material, with no note in the file. A carryforward that did not proforma, which is a known enough phenomenon that Intuit publishes a help article on why some client data does not proforma. A deduction that is defensible but that this firm, for its own risk reasons, does not take without a partner conversation. Lacerte will never flag any of those, because none of them are diagnostics. They are firm policy.

What a commissioned layer does. Reads the in-progress return through ODBC, reads the prior year, reads the workpapers out of the DMS, and runs your checklist. Not a generic checklist. The one your reviewer would run, written down for the first time, versioned, and applied to every return rather than to the ones that reach the reviewer before the deadline. The output is a flag list attached to the return with a citation for each flag, so the reviewer starts from a shortlist instead of from page one.

The ceiling. This is an assistive layer and it stays one. It does not sign anything, it does not clear a flag, and it does not reduce reviewer headcount in year one. What it does is move review earlier in the cycle and make it consistent across the whole population instead of the top third. Firms that pitch this internally as a headcount story get resistance and deserve it. Pitched as "your reviewer sees every return instead of some of them," it lands.

What Lacerte already does. The Missing Data Utility borders the fields that are missing information and will send the request out to the client, either to their Intuit Link portal or by email. Link tracks the document exchange. Between them, the first request is well handled.

Why it still fails. The first request is not the problem. The fourth is. A firm sends the organizer, sends the reminder, and then the chase collapses into an admin's spreadsheet and a set of phone calls that nobody has time to make in the last three weeks of March. The work is not intellectually hard and that is exactly why it does not get done: it is the lowest-status task in the building during the highest-pressure fortnight of the year.

The pattern that works. A persistent, multi-channel follow-up layer that owns the sequence rather than the first touch. It reads the outstanding-item list, escalates channel over time (portal notification, then email, then a call), stops the moment the document lands, and keeps a per-client record of what was asked and when. The reason this is worth automating and not staffing is that the value is entirely in the persistence, and persistence is the thing humans stop doing under load.

The proof we have, stated honestly. This is the one workflow on this page where we can point at shipped volume, and it is not from a CPA firm. Jim Glaser Law runs five channel-specific voice agents we built, across PPC, Organic, TV, Meta and LSA, which have handled 3,787 calls and 5,514 minutes and give the firm per-channel attribution on answered calls. A multi-location home services operator runs the same pattern at 1,486 calls and 2,203 minutes. Across all clients the total is past 6,000 live calls. The mechanics of an outbound sequence that keeps calling until it gets the thing are identical whether the missing item is a signed retainer or a brokerage statement. The vertical is not. Read it as evidence that the machinery works, not as a CPA reference, because it is not one.

What Lacerte already does. All of it, on a pull basis. Status lives in the Clients list, in the Federal and State e-file status columns; F4 on a highlighted client opens the client status window with an e-File Status tab. You retrieve statuses from the E-file menu under Step 3, e-File Acknowledgement Statuses, then either Receive Acknowledgement Statuses for everything or Update Acknowledgement Status for Selected Return(s). Received at Lacerte means the return has reached Intuit and is being processed for onward transmission to the agency. Accepted means the agency took it. Federal acknowledgements are usually available in one to three days, state acknowledgements in two to five business days. Rejections are visible through the e-file Activity Report, reached from the E-file menu under e-file Reports/Messages, which you can filter down to IRS Rejected and State Rejected.

The gap is not capability, it is attention. Every one of those steps requires a human to open Lacerte, navigate to a view, and choose to look. On April 14 at nine in the evening, nobody is looking. A federal rejection sitting unread for 36 hours in the wrong week is a genuinely expensive event, and the firm usually finds out because the client calls.

The build, and an honest label on it. A scheduled job holds an ODBC read against the datapath, diffs acknowledgment state since the last pass, and pushes: pages the assigned preparer on a rejection with the reject code and the client, posts an accepted notice to the client without anyone drafting it, and keeps a running board of everything still in Received at Lacerte past its normal window. This is the highest-return item on the page relative to build cost, and it is barely AI. It is a poller, a diff and a notifier, with a language model doing nothing more than writing the client-facing sentence. We say so because a vendor who calls this AI is telling you something about the vendor.

The ceiling. Polling interval. You are reading a datapath, not receiving a push, so your floor on latency is however often you are willing to run the job and whatever load that puts on the file share during the busiest fortnight of the year. Fifteen minutes is comfortable. Real-time is not on offer, and any vendor promising it on Lacerte should be asked how.

Why this one is underrated. Extensions are the most automatable thing a tax practice does, because almost none of it is judgment. The population is knowable in February. The criteria are mechanical: who has not delivered, who always extends, who has a K-1 that is not coming before September regardless. The output is a form and a payment estimate. Firms handle it manually anyway, in the exact week they have the least capacity, which is how a client ends up extended without a payment and with a penalty conversation in October.

What the layer does. Selects the population off the datapath against the firm's own rules rather than a gut call. Drafts the payment estimate from prior-year liability plus current-year known items, presented as a worked calculation the preparer approves or overrides, never as a filed number. Generates the client-facing note explaining what is being filed and what they owe by the deadline, in the firm's voice, one per client. Tracks who has been told, who has paid, and who is still silent, and hands the silent list back to the chase sequence from workflow four.

The ceiling, and it is not negotiable. The payment estimate is a preparer sign-off, every time, with no batch approve. The tempting version of this build is one that files the whole population unattended. Do not build that one. The failure mode is silent, it is financial, it belongs to the firm and not to the software, and the time saved does not come close to covering it.

Intuit publishes a set of generative AI tax features, Intelligent Data Import for source-document extraction, Smart Navigation, and an AI assistant that reviews returns against its diagnostics library. Those are published on the ProConnect Tax Online product page. They are not claimed for Lacerte or ProSeries. That is the single most useful thing a Lacerte firm can know about Intuit's AI roadmap, because it tells you where the investment is going: into the cloud product.

On the Lacerte side, the integrations page names Intuit Tax Advisor as the AI-driven advisory planning piece, alongside Link, SmartVault, the Document Management System, Tax Scan and Import, Financial Institution Download, Quick Employer Forms, Intuit Sign, the Tax Planner and Analyzer, and QuickBooks Desktop Accountant trial balance transfer. That is a real feature set and a firm should exhaust it before commissioning anything.

The strategic read: if Intuit's generative AI investment lands in ProConnect first, a Lacerte firm has a choice between waiting for a migration it did not ask for and building the specific pieces it needs on the SDK now. Neither answer is automatically right. It depends on how firm-specific your workflow is, which is the question in what actually works for CPA firms.

The best public documentation of what a Lacerte SDK integration actually costs to deploy is not Intuit's. It is SurePrep's install guide, written for their own customers, and it is worth reading before you scope anything, because your build inherits every line of it.

Install goes on workstations and local machines, not the server. You need both the 32-bit and 64-bit builds. You need the Visual C++ 2015 redistributable in place first. You need administrator rights. Any previous SDK version has to be uninstalled. And the line that matters most operationally: Lacerte sign-in credentials have to be entered again when the session expires after 24 hours.

Read that last one carefully against an unattended overnight job. A poller that needs a human-authenticated session that lapses daily is not unattended. There are architectural answers, and they all involve a decision about where the integration process runs and who owns the credential, which is a security conversation with your IT lead, not a footnote. If your Lacerte is on Rightworks, Verito or a private cloud image, that conversation includes your host.

None of this is a reason not to build. It is a reason to scope it with the host and the IT owner in the room in week one, which is why data readiness is the first thing we assess and not the last.

An ODBC read against a Lacerte datapath returns social security numbers, income detail, bank information for direct deposit, and dependants' identifying information for the whole client base. That is a materially different security posture from a marketing automation, and any scoping conversation that does not open there is the wrong conversation.

Three positions we hold and will not move on. The data stays inside the firm's own environment; the processing runs in the firm's tenant, not in ours. Anything sent to a model provider is scoped to the specific task and logged, and the firm sees the log. And the firm gets a written data-flow diagram before the build starts, not after, because a data-flow diagram you cannot draw is a design you do not have.

The questions a firm should be asking any vendor here, including us, are listed in the security questions to ask before an AI build. A vendor who cannot answer them in writing is not ready for your client list.

We have not shipped a Lacerte commission we can point you at. There is no CPA reference call at the end of this page, and if a competitor's Lacerte page offers you one, ask for the firm's name and the partner's number before you believe it.

What we have shipped, and what you can check: Jim Glaser Law, nameable, five channel-specific voice agents across PPC, Organic, TV, Meta and LSA, 3,787 AI-handled calls and 5,514 minutes, giving the firm per-channel attribution on answered calls. Jimmy takes reference calls. Beyond that, and anonymised by agreement: a multi-location home services operator at 1,486 calls and 2,203 minutes, a regional 3PL and warehousing operator at 211 calls, a realty firm at 148 calls, and past 6,000 live calls in total across the client base.

The engagement most relevant to a tax practice is a 47-attorney litigation firm whose matter, invoice and IOLTA trust accounting all run on a platform we commissioned: 13,296 matters, 4,396 clients, 5,684 invoices, and trust reconciled byte-identical. That is reconciliation-grade financial software on a regulated professional-services stack, under rules that punish a rounding error the way yours do. It is the closest honest analogue we have to a tax practice. It is not a tax practice, and we are not going to describe it as one.

Two marketing agencies also outsource their AI fulfilment to us, which is worth knowing mainly because it tells you what we are: a build shop, not a reseller. ColabContent LLC has been operating since 2020 on the content side, with the AI practice running since 2024, out of Boston. The full boundary of what we decline to build is published.

It does not earn it if your problem is extraction. Scan-and-populate is mature, it supports Lacerte, and the vendors have spent years on document coverage you are not going to replicate. Buy it. It also does not earn it if you are a fifteen-person shop where one workflow touches four hundred returns; the fixed fee will not amortise, and packaged tools plus better process discipline is the honest recommendation. We turn that engagement down rather than take it.

It earns it when the thing you need automated is specific to your firm and therefore cannot be bought: your expected-document logic, your review checklist, your chase sequence, your escalation rules, your extension criteria. Those are the parts of the practice that make you different from the firm across town, which is exactly why no product ships them. Volume is the other half of the test. One workflow, several hundred returns or more, repeated every season, is where the arithmetic works.

The commercial shape. Fixed fee between $45,000 and $180,000, set after the diagnosis call and after the integration depth is named, not before. Five to seven weeks for a read-and-suggest build, longer if it writes back through the SDK API. The firm owns the integration code, the prompts, the model selection and the pipeline at handoff, with no retained licence and no dependency on us. Full pricing detail is on the pricing page, and the cost question specific to accounting practices is worked through in what AI consulting costs a CPA firm.