Member of a professional association? Exclusive member pricing is available through participating associations.

Product4 min read

Why Taxably does not type into your tax software

Half the products in this market want to enter data into your tax software, and a few want to prepare the whole return. We stop at the prep sheet on purpose. Here is the reasoning.

The obvious roadmap for a product like ours is to keep going: once you have recognised every document and read every box, why not push the numbers straight into Lacerte or Drake and hand the preparer a populated return? Several well-funded companies are building exactly that, and for some firms it will be the right purchase.

We decided against it, and the decision is load-bearing enough that it shapes the whole product. Three reasons.

The preparer should own every number

A populated return invites a different review posture than a blank one. When software has already filled the fields, the human's job quietly shifts from entering what they verified to spot-checking what the machine asserted, and the errors that survive are the ones nobody typed. We would rather hand the preparer a packet that makes entry fast and verification easy: the headline value on each document card, flags where this year disagrees with last year, and the original document one bookmark away. The number gets into the return because a licensed person put it there.

Integrations are a tax you pay forever

Every product that writes into tax software carries a compatibility matrix: this version of UltraTax, that version of CCH, three of the dozen platforms firms actually run. The matrix decides who can buy the product and breaks a little every release cycle. Our prep sheet is keyed to the structure of the return itself, the IRS form families and schedules, so it reads the same next to any software, including the platforms the integration vendors skip, and it keeps working when a firm switches.

The privacy boundary stays clean

Driving tax software means holding the real data that tax software holds: names, SSNs, the works, in the vendor's cloud, under the vendor's controls. Our approach only works because we never need to keep the identities at all; placeholders are enough to sort a pile and build a packet. The moment we offered to type into your software, that boundary would have to move. We think the boundary is worth more than the feature.

So the scope line is deliberate: Taxably identifies, organizes, verifies what should exist, and assembles the packet. The judgment, the entry, the signature, and the filing stay where they belong, with your firm.

See the prep sheet for yourself

How it works shows what a real prep sheet holds, built from a sample client folder.

See how it works