What GruntWorx and SurePrep automate, and where a depreciation schedule falls outside it

A firm that has already bought document automation asks a reasonable question when a new client arrives: we run GruntWorx, or we run SurePrep — does it handle this?

The document in hand is a prior preparer's depreciation schedule. Forty pages, 200 assets, printed out of Lacerte or UltraTax by a firm that is no longer in the picture.

The answer is not a criticism of either product. It is that a depreciation schedule is a different kind of object than the ones they were built to read, and the difference is worth understanding before you scan it and wait.

Source documents and workpapers are different objects

Document automation in tax is built around source documents — the things a taxpayer receives from a third party and hands to their preparer. A W-2 comes from an employer. A 1099-B comes from a broker. A K-1 comes from a partnership. Each has a defined layout, a known issuer, and a fixed set of boxes, which is exactly what makes automated extraction tractable and why coverage is published as a list of form numbers.

A depreciation schedule is not one of those. Nobody issued it to the taxpayer. It is a workpaper — a report printed out of one firm's software, in a layout that firm's software chose, carrying the positions the prior preparer took. There is no form number. Two schedules for the same client from two suites do not share a column order, a heading vocabulary, or even a convention about whether §179 sits inside the current depreciation column or beside it.

That is also why it arrives at a different moment. Source documents arrive with the client's tax year. A depreciation schedule arrives when you inherit a client mid-relationship, or when the firm changes software and the whole book has to move.

What GruntWorx Populate covers

GruntWorx publishes its supported forms, and the list is specific: W-2, W-2G, the 1099 series (B, DIV, G, INT, MISC, NEC, OID, R) and Consolidated 1099, 5498, RRB-1099, SSA-1099, 1095-A, 1098, 1098-E, 1098-T, and K-1s from 1041, 1065 and 1120S returns. It populates into CCH Axcess, CCH ProSystem fx, Drake Tax, Lacerte, ProSeries, GoSystem Tax RS and UltraTax CS.

Depreciation schedules and fixed asset listings are not on that list, and Drake's own knowledge base describes the three GruntWorx products as organising documents, populating form data, and importing trades. Trades is the investment-transaction path — the 1099-B problem, not the 4562 problem.

None of that is a gap in the product. It is a product that says what it does.

What SurePrep 1040SCAN covers, with one nuance worth catching

1040SCAN reads IRS forms, organizer pages, brokerage statements, grantor letters and government output forms, and integrates with CCH Axcess, CCH ProSystem fx, GoSystem Tax RS, Lacerte and UltraTax CS. Its documentation is explicit that organizer pages count as standard documents for 1040 returns, which matches the name.

The nuance: its coverage does include a Detail Depreciation organizer page for certain platforms. That deserves precision rather than a flat "no depreciation".

An organizer page is a page your own software generated, in your own organizer, in a layout the scanning product already knows, carrying data that originated in your system. A prior preparer's depreciation schedule is the opposite on every one of those counts: another firm's software, another firm's layout, and data that has never been in your system at all. Recognising the first is a solvable formatting problem. The second is the reason this niche exists.

So the honest reading is that 1040SCAN handles a depreciation page that came out of your workflow, not a depreciation schedule that came out of someone else's.

Where both are stronger than we are

Stating this plainly, because a comparison that only runs one direction is not worth reading.

Destination coverage. GruntWorx populates seven suites; 1040SCAN integrates with five. We support three — Drake, Lacerte and ProConnect. UltraTax through Fixed Assets CS is next in our queue and is not shipping. ATX and CCH are not supported at all, as sources or destinations.

Breadth of document. Both take the entire pile a 1040 client drops off and cut real hours out of a return. We read one document type. If your problem is the January-to-April volume of W-2s, 1099s and K-1s, neither of them is replaced by anything here.

They are the incumbent workflow. A firm already running one of them has scanning, review and routing in place. Nothing about a single-purpose conversion asks you to change that.

	GruntWorx Populate	SurePrep 1040SCAN	This tool
Reads	current-year income and information forms	1040 source documents, organizer pages, brokerage statements	a prior preparer's depreciation schedule or fixed asset report
Return types	the 1040 form set	1040-centred	1040, 1065, 1120, 1120S, 1041, 990
Depreciation	not on the published forms list	a Detail Depreciation organizer page, on some platforms	the entire product
Writes into	7 suites	5 suites	Drake, Lacerte, ProConnect

Coverage as published in August 2026. All three change; the published list is the thing to check, not anyone's summary of it, including this one.

The three questions that settle it for any tool

If you are evaluating anything for this job, these separate the products quickly.

Does it read another firm's report, or forms with a fixed layout? This is the whole distinction above, and it decides the answer before any feature comparison starts.

Does it produce a file the destination actually imports? Extraction and import are different problems. Drake's 4562 import is 104 positional columns where the order is the contract; Lacerte's fixed asset import reads CSV and XLS but not XLSX. A tool that gives you a clean spreadsheet has done half the job.

How does it prove the transcription is right? For a 200-asset book, this matters more than anything else on a feature list. The only independent evidence available is the set of totals the schedule itself printed — tie the extracted rows against them, per group and in total, or you are trusting a transcription because it looks tidy.

What we do with it

One document type, three destinations, and a gate. A depreciation schedule PDF goes in; a Drake, Lacerte or ProConnect import file comes out, and it is not downloadable until the totals printed on the source match the totals summed from the extracted rows at a dollar's tolerance.

It transcribes and does not decide. A component the schedule never printed — prior §179 and prior bonus on a Lacerte summary variant, a state treatment absent from a federal report — comes back empty and flagged rather than zeroed, which blocks the download until a preparer resolves it deliberately.

That narrowness is the trade. It does nothing with a W-2. It is built for the prior year depreciation schedule a new client brings, and for the software switch where a whole book of assets has to move at once.

FAQ

Does GruntWorx import a depreciation schedule into Drake?

Not according to its published forms list, which covers W-2s, the 1099 series, K-1s, 1098s and 1095-A. Its Trades product handles investment transactions rather than fixed assets. Check the current list directly, since coverage changes between seasons.

Does SurePrep 1040SCAN handle fixed assets?

Its source document coverage includes a Detail Depreciation organizer page for certain platforms — a page generated by your own software in your own organizer. That is a different document from a prior preparer's depreciation schedule printed out of another firm's suite.

Why is a depreciation schedule harder to automate than a 1099?

A 1099 has a form number, a fixed layout and a known issuer. A depreciation schedule is a report whose layout the printing software chose, so column order, heading vocabulary and even whether §179 sits inside the current depreciation column vary by suite and by print option.

Can I use one of these alongside a conversion tool?

They address different documents at different points in the year, so nothing overlaps. Source document automation runs against the current year's pile; a schedule conversion runs when a client is inherited or a suite is changed.

Which suites can a converted schedule be imported into here?

Drake, Lacerte and ProConnect today. UltraTax through Fixed Assets CS is next in the queue. ProSeries has no direct asset import at all, and ATX and CCH are not supported.

How do I verify any of this rather than take a vendor's word?

Ask for the published document coverage list rather than a description of it, and confirm the output format against the destination's own import specification. Both are checkable in an afternoon and neither requires a demo.