Lacerte is a trademark of Intuit Inc. This article is general guidance, not Intuit documentation. Import features, menus and supported formats change between versions; always confirm against Intuit's current Lacerte help resources.
What does "importing" mean in a Lacerte workflow?
Bringing data into a client file from an electronic source rather than typing it. Instead of a preparer keying each W-2 or 1099 box, values arrive from a file and the preparer reviews them.
Firms typically encounter several kinds of import: carrying forward prior-year client data, bringing in data from other software or services, and bringing in transaction or information-return data. Each has its own mechanics in Lacerte, and availability varies by version and license.
When is importing worth it, and when is manual entry better?
Importing pays off when the same structured data would otherwise be typed by hand, especially for clients with many documents. Manual entry can still be simpler for a client with a single short form.
- Good candidates: clients with multiple W-2s and 1099s, brokerage statements with many lines, and recurring clients with consistent document sets.
- Weaker candidates: one-off forms with two or three values, documents with handwritten changes, and anything where you need to make a judgment as you enter it.
How should a firm test an import path before tax season?
Use a small set of test or sample clients, import, and compare every value against the source documents before using the path on live returns.
- Create test clients in a non-production environment or clearly labeled test files.
- Import data for a range of document types: W-2, several 1099 variants, and a K-1.
- Compare each imported value with the source, box by box.
- Check how the import handles multiple documents of the same type, such as two W-2s.
- Note anything that has to be completed manually after import.
- Write down the steps so every preparer follows the same procedure.
What are common pitfalls with imported data?
Duplicates, data landing on the wrong taxpayer or spouse, missing state information, and assumptions that "imported" means "reviewed."
- Duplicates: importing the same document twice, or importing after someone already keyed it.
- Taxpayer vs. spouse: confirm that each document is attributed to the right person on joint returns.
- State items: state wages and withholding often need particular attention.
- Corrected forms: make sure a corrected 1099 replaces the original rather than adding to it.
- Supplemental information: K-1 footnotes and brokerage supplemental pages may not translate into simple fields.
How do you keep review in place?
Review twice: once when data is extracted from source documents, and again as part of your normal return review in Lacerte.
The first review confirms that what was captured matches the document. The second confirms that the return makes sense as a whole. Neither replaces the other.
Where does NiniTaxBot fit for Lacerte firms?
NiniTaxBot handles the steps before Lacerte: clients upload documents to a secure portal, AI classifies them and extracts the data, and your team reviews and approves the values beside the source documents. A Lacerte export is coming soon; it is not available today, so this guide describes import practices generally. NiniTaxBot is not affiliated with or endorsed by Intuit; see NiniTaxBot for Lacerte firms for details, and start with our overview of eliminating manual W-2 and 1099 entry.
How should source documents be prepared before import?
Make sure each document is complete, legible, classified correctly and attributed to the right client before any data is exported for import.
Import quality can only be as good as the input. A missing page of a brokerage statement, a cropped photo or a document filed under the wrong client produces a clean-looking file with wrong data. A short pre-import routine helps:
- Confirm every page of multi-page documents is present.
- Confirm the taxpayer name and identifying number match the client.
- Check whether the document is an original or a corrected version.
- Resolve anything flagged as uncertain during extraction.
Who on the team should own imports?
Name an owner for the import procedure and an approver for each client's data. They can be the same person in a small firm.
In busy weeks, "someone already imported that" is a common cause of duplicates and gaps. Writing down who approves data and who brings it into Lacerte, and recording when it happened, keeps everyone aligned. It also gives you a clear point to improve next year: if a type of document keeps needing manual fixes, the owner can decide whether to keep importing it or enter it by hand.
What should you document after the season?
Keep a short log of what worked, which document types needed manual completion, and any import issues by Lacerte version. That log is the best input for next year's procedure and for conversations with any vendor whose data you import.
A checklist for Lacerte firms
- Confirm your Lacerte version and the import options it offers.
- Test with sample clients before the season.
- Document the import procedure for your team.
- Assign responsibility for approving data before import.
- Keep your normal return review and diagnostics in place.