Tax Source Document Automation and the Work Between Upload and Prep

Getting a source document into your firm is only the first handoff. A client may send a W-2, 1099, K-1, brokerage statement, or supporting file through a portal, secure link, email, scan, or another process your team already uses. That file may still need to be identified, matched, organized, checked for missing information, and connected to the preparation work that follows.

‍

Tax source document automation addresses that gap. Soraban focuses on moving incoming documents toward prep readiness without asking firms to replace useful collection processes or hand tax judgment over to software.

‍

By the time a preparer opens the engagement, the team should know what came in, where it belongs, what is still outstanding, and what can move forward. That's the difference between receiving a file and having an engagement that's actually ready for prep.

‍

Request a Demo

What document automation actually covers after upload

Document automation handles the repeatable work that starts once a file reaches the firm. That can include identifying the document, matching it to the right client or engagement, organizing it consistently, surfacing items that need attention, extracting relevant information, and preparing information for the next stage of tax work.

‍

One part of that process is optical character recognition (OCR), which can convert text in scanned or image-based files into machine-readable text. OCR handles the reading step, and AI can then add context, such as recognizing a form or locating relevant fields across different layouts. But reading the document is only one part of the handoff.

‍

A W-2 has to land in the right engagement before anyone works with the values on it. A brokerage statement needs to be organized with the rest of the supporting material before that information is useful downstream.

‍

Don’t stop at whether the software can read the document. Look at what still has to happen before the information is ready for the next stage of tax work.

An upload is a handoff, not a prep-ready file

A document is received when the firm has the file. It becomes prep-ready when a preparer can open the engagement and begin substantive work without first sorting out what arrived, where it belongs, or what is still missing.

‍

The portal, organizer, inbox, or paper process may already be doing its job. What remains is the internal handoff: identifying the file, confirming the client and year, matching it to the engagement, and seeing what is still outstanding.

‍

That's the gap between collection and preparation. A folder can contain every file the client has sent and still require another round of sorting, matching, or follow-up before the preparer can use it.

What a prep-ready engagement should contain

A prep-ready engagement gives the preparer a clear starting point for tax work. It's organized and usable, but it isn't necessarily complete, reviewed, or free of open questions.

‍

The preparer should have:

‍

  • Files tied to the correct client and engagement year
  • Consistent naming and organization
  • Visibility into what has arrived and what is still outstanding
  • Clear flags for items that need attention
  • A workpaper file with source documents already tied to the supporting work

‍

Prior-year information can add useful context around expected documents and current-year questions, but it should remain a reference point. A missing K-1 may be an open item, or it may reflect a real change in the client's situation.

‍

Prep readiness means the preparer can understand the engagement, see what is open, and begin the work without retracing intake. Tax judgment and review come next.

Classify, match, and organize the source documents first

Before anyone works with the tax values inside a file, the firm needs to know what the document is and where it belongs. One client may send W-2s, 1099s, K-1s, brokerage statements, supporting schedules, scans, photos, and corrected files at different points in the season.

‍

Soraban Collect handles that intake work by naming, matching, and organizing incoming files within the engagement. That gives the preparer a cleaner starting point without requiring staff to open, rename, and file every upload by hand.

‍

Classification and extraction are separate jobs. Recognizing a file as a W-2 and matching it to the right taxpayer comes first. Pulling wages, withholding, and other values from that form comes later.

‍

Keeping those steps separate means the preparer starts with documents that already have context, rather than sorting files while preparing the return.

Surface missing items and document issues before prep

An organized engagement can still be incomplete. Knowing where each file belongs doesn't tell the team that every expected item has arrived or that every upload is ready to use.

‍

Before prep begins, staff need a clear view of what is in and what is still open. Checklists, questionnaire responses, prior-year context, and other engagement information can provide that reference point. Collect can track missing items as files arrive, so follow-up stays connected to the engagement.

‍

Some uploads need attention. A scan may be hard to read. A file may be incomplete, unexpected, or difficult to match with confidence.

‍

The earlier those issues are visible, the less likely the preparer is to uncover basic intake questions halfway through the return. Routine follow-up can stay with the team managing intake, while tax questions move to the people responsible for the technical work.

Request a Demo

Let prep work begin before the last document arrives

Prep work can begin before every outstanding document is in. An incomplete return may need additional information before it can be completed or reviewed, but the parts that are ready can begin moving.

‍

In a batch-based process, the firm may collect documents first, then organize the file, build the binder, populate leadsheets, and prepare workpapers. A late K-1 or brokerage statement can leave the next stage waiting for that final batch.

‍

With Soraban Prepare, the workpaper layer can begin taking shape as documents arrive. Prepare can populate the binder, leadsheets, and workpapers while the engagement is in progress, giving the preparer useful work to start with instead of waiting for intake to close.

‍

That reflects how clients actually submit information. Late documents may raise questions or require additional review, but they can still be entered into an engagement where prep is already underway.

Binder, leadsheet, and workpaper play different roles

The binder is the full engagement file. The leadsheet is the summary or control layer for a section. The workpaper contains the detailed support behind a number or a conclusion.

‍

Each serves a different purpose for prep and review. The preparer needs the detailed support in the right place, while the reviewer needs a clear path from the section summary back to the underlying work.

‍

Prepare can populate those layers as documents arrive while keeping the accountant's annotations and edits intact. That lets the file continue taking shape without undoing work the team has already done.

Keep each amount connected to its supporting source

As the workpaper layer takes shape, preparers and reviewers need a clear path back to the source.

‍

A number in a workpaper should stay connected to the document behind it. If a reviewer questions an amount, the supporting file should be easy to find. If the preparer makes a correction, the source should remain close enough to the work to understand what changed and why.

‍

That traceability also leaves a clearer audit trail for sign-off and later review. It can support compliance documentation by keeping source documents tied to the work they support, without replacing professional review or firm policies.

‍

Instead of searching through unrelated PDFs to reconstruct where a figure came from, the reviewer can spend that time evaluating the work itself.

Turn processed source documents into usable tax data

With the source files organized and the workpaper layer taking shape, the next handoff is getting reviewed tax information into the firm's tax software:

‍

  • Recognize the tax form
  • Extract the relevant fields
  • Review and validate the information
  • Move approved data into tax software

‍

OCR alone doesn't complete that sequence. The relevant values need to be identified, mapped to the right fields, and checked before they move downstream.

‍

Soraban Connect handles this stage: tax form recognition, data extraction, field mapping, validation, review before export, and tax software data entry. It picks up after Collect has organized the files and Prepare has built the workpaper layer.

‍

Connect supports data movement into UltraTax, CCH Axcess, Lacerte, and Drake. The file may already be organized and prep ready, but the information inside it has a separate handoff into tax software.

Keep accountant control visible as automation continues

That handoff needs accountant oversight. Automation can remove repetitive keystroking without turning extracted information into an automatic final answer.

‍

In Prepare, accountant annotations and edits stay intact as the workpapers develop. Prepare can also draft reviewer notes, but the tax team decides what to approve, edit, or reject.

‍

Connect adds another review point before export. Staff can review and validate extracted information, then address anything that doesn't look right before it moves into tax software.

‍

A difficult-to-read document, conflicting amount, or tax question may need a preparer or reviewer to make the call. Those exceptions should stay visible and with the right person.

‍

The repetitive work can move to software. The tax judgment doesn't.

‍

Request a Demo

Evaluate the handoff, not only the extraction percentage

Extraction accuracy matters, but it only tells you how reliably the software captures fields. It doesn't tell you how much work remains around that step.

‍

One way to evaluate the handoff is to follow a single engagement across the points where work changes hands. Look at which steps still require professional judgment and which ones mainly repeat handling the system has already done.

‍

‍

Workflow point What to verify Work that may still remain
Receipt and matching Does each upload land with the correct client, year, and document context? Opening files one by one, renaming them, relocating them, or confirming ownership manually
Completeness Can staff see what was expected, what arrived, and what is still outstanding? Separate tracking sheets, repeated portal or inbox checks, or preparers discovering missing items during prep
Prep setup Can the binder, leadsheets, and workpapers begin taking shape from incoming documents? Waiting for a final batch, rebuilding sections manually, or moving support into place after intake closes
Source traceability Can a preparer or reviewer trace a figure back to its supporting source for review, audit support, or compliance documentation? Hunting through PDFs, reconstructing support, or asking another staff member where an amount came from
Data extraction and review Are relevant fields identified, mapped, and available for review before they move downstream? Retyping values, comparing source documents with extracted data in separate places, or correcting information after the fact
Tax-software handoff What reviewed data moves into the firm's tax software, and what still has to be entered again? Duplicate data entry, manual imports, or another reconciliation step between systems
Exceptions and control Are unclear items visible, reviewable, and routed to the person who owns the decision? Exceptions buried in notes or email, unclear ownership, or staff rebuilding context before they can resolve the issue
Existing systems Can the workflow keep working with the practice management and tax software the firm already depends on? Moving the same information between disconnected steps or rebuilding work because one system can't carry context into the next

‍

No single row decides whether the automation is useful. Look at the pattern across the engagement. If one task disappears only to create another downstream, the work has moved rather than gone away. If routine handling falls away while review and judgment stay clear, the handoff is doing more of what the firm actually needs.

‍

For a real test, run a representative engagement through these points and note every place where someone has to reopen, rename, re-key, re-request, or reconstruct context. That gives the firm a practical view of what the software changes once it's working with the files and systems the team actually uses.

Where Soraban fits between document intake and the finished return

Soraban is the execution layer between the tools your firm already uses to organize work and calculate returns.

‍

Practice management organizes work. Tax software calculates returns. Soraban moves work through the firm.

‍

Soraban supports those workflows through four products:

‍

  • Collect handles intake, questionnaires, reminders, missing-item tracking, file handling, and uploaded-document organization
  • Prepare builds and populates binders, leadsheets, and workpapers while preserving source connections and accountant edits
  • Connect handles tax data extraction, field mapping, validation, review before export, and entry into UltraTax, CCH Axcess, Lacerte, and Drake
  • Deliver handles return packets, 8879s, signatures, payments, reminders, and closeout

‍

For the work between upload and prep, Collect gets incoming files organized and keeps open items visible. Prepare builds the workpaper layer as those documents arrive. Connect takes the reviewed information into the next stage of tax-software data entry, while Deliver handles the later client-facing steps.

‍

Together, those products sit alongside the firm’s practice management and tax software. The aim is to remove the manual rebuilding between stages while keeping source information, status, and review clear as the engagement moves forward.

Frequently asked questions:

1) Does document automation replace a client portal or organizer?

No. A portal or organizer can still handle client requests and document collection. Document automation picks up after files arrive, helping with matching, organization, tracking, and prep-related setup.

‍

What matters is how much manual handling remains between receiving the documents and giving the preparer a usable engagement.

‍

2) How can prior-year return information help with document intake and prep?

Prior-year information gives the firm useful context for current-year requests, expected documents, and engagement structure. It can make questionnaires and checklists more relevant and help staff spot when an expected item hasn’t arrived.

‍

Current-year changes, new forms, and client circumstances still need review.

‍

3) What happens when clients upload scans, photos, or different file types?

Soraban Collect can handle common file types and varying scan quality, then name, match, and organize uploads within the engagement.

‍

An unclear or poor-quality file may still need staff review or client follow-up. Getting the file into the firm doesn’t always mean the source is ready for prep.

‍

4) How can document automation help standardize workpaper structure across a firm?

Document automation can bring more consistency to naming, organization, and workpaper structure across similar engagements. That gives preparers and reviewers a more familiar file to work through while preserving firm conventions that still serve a purpose.

‍

5) What happens when another source document arrives after prep has started?

With Soraban Prepare, a new document can enter an engagement where work is already underway. The binder, leadsheets, and workpapers can continue developing as additional files arrive.

‍

A late item may require more prep or review, but it doesn’t have to hold the rest of the engagement in place while the team waits for one final batch.

‍

6) What kinds of tax documents can document automation process?

Common examples include W-2s, 1099s, K-1s, brokerage statements, and other supported forms.

‍

Coverage varies by software, so firms should test the document types and engagement scenarios they actually handle rather than relying on a general coverage claim.

‍

7) Who should review exceptions before tax data moves into tax software?

That depends on the firm's review structure and the issue involved. The preparer, reviewer, accountant, or other authorized staff member responsible for that step should be able to see and resolve the exception.

‍

Soraban Connect keeps extracted information reviewable before export, so unresolved items can be addressed before the data moves into tax software.

‍

8) Does automating this work require replacing practice management or tax software?

No. Soraban works alongside the tools and workflows the firm already uses. Practice management can continue organizing engagements, tax software can continue calculating returns, and Soraban handles execution work between those stages.

‍

9) Can admins own more of the document workflow without taking over tax judgment?

Yes. Admins can manage requests, reminders, missing-item follow-up, file handling, and organization without becoming responsible for tax conclusions.

‍

Preparers, reviewers, and accountants still own the judgment needed to resolve technical questions and complete the return.

‍

10) What should a firm test before expanding document automation across more returns?

Use the firm's actual files and workflow. Test how documents are matched and organized, how missing items and exceptions are surfaced, how the workpaper file develops, and what happens before reviewed data reaches tax software.

‍

Include straightforward engagements along with late documents, corrected forms, and unclear scans. The test should show what the software handles well, where staff still need to step in, and how much manual work remains around the process.

‍

Conclusion

Getting the file is only the start. The real work is turning incoming documents into organized, traceable, reviewable inputs that a preparer can actually use.

‍

Soraban works alongside the systems firms already use to handle more of that execution work. Accountants keep the judgment, while Soraban takes on more of the repetitive steps required to move the engagement forward.

‍

Request a demo to walk through your firm’s current document workflow and see how Soraban handles the work across intake, prep, data entry, and delivery.

‍

Explore More Tax Workflow Topics

‍

GET STARTED

Tell us about your firm. We'll build the workflow.

Under 30 days to your first live season. No migration. No commitment until you see it working.

Onboard in one week
First season automated. ROI visible before renewal
No sales cycle. No commitment until you're live