FOR TAX PROFESSIONALS|FIND A TAX PROFESSIONAL

04 / Deliver

Design-partner validation

Approved data moves to your tax engine, and signature, invoice, payment gate, and client communication finish in the same workflow.

The last mile — handoff, signature, invoice, and the client conversation — lives in three other tools and a mail merge.

Handoff, signature, communication, billing, archive.

01/Capabilities

What Deliver does today.

Tax-engine handoff

Design-partner validation

Approved data moves into the professional tax software your firm already uses.

Scope Moving approved, structured data toward the firm's tax engine.

Limit Mechanism and coverage differ per engine and are stated on each integration page.

Verified 2026-08-01

E-signature

Available now

Signatures are collected in the same workflow as the return.

Scope Engagement letters and the common authorization forms.

Verified 2026-08-01

Invoicing and payment gate

Available now

Invoice and payment sit in the workflow, and delivery can wait on payment.

Scope Invoice, payment collection, and gating delivery on payment.

Verified 2026-08-01

Archive

Available now

Completed work is retained under TaxScout's product retention policy.

Scope Retained client archive under the product retention policy.

Verified 2026-08-01

02/Scope

What is in scope today.

  • Structured export toward the firm's professional tax software
  • E-signature on the common engagement and authorization forms
  • Invoicing and payment gating
  • Client communication and archive

03/Filing

Where calculation and e-file happen.

TaxScout e-files supported federal and state returns through IRS MeF under your firm's EFIN — or hands approved data to the professional tax software your firm already uses. E-file coverage is published per return type, and nothing is transmitted before the reviewer approves and the 8879 is signed.

That is a statement about today, not a doctrine. Approved data moves into the professional tax software the firm already uses, and the exact handoff mechanism for each engine is published on its integration page rather than implied by a logo.

Integration status by engine →

04/Security

What happens to the data at this stage.

  • Client documents and tax data are encrypted during transmission and while stored.
  • Each firm operates in a logically isolated workspace, and access is assigned according to responsibility.
  • Multi-factor authentication and role-based access are available.
  • Material actions involving documents, client data, review, and financial information are recorded with the actor and timestamp.
  • TaxScout maintains encrypted backups that support recovery and continuity.
  • Customer data is not used to train shared models.
  • TaxScout hosts customer data in the United States.
  • Security controls are mapped to relevant professional-firm requirements.

Control detail and current assurance status: /security.

·/Limitations

What this does not do today.

  • Direct e-file coverage is published per return type; business e-file is in design-partner validation.
  • Engine handoff mechanisms carry an exact per-engine status — see the integration pages.
See one return move through this

A single 1040 from client documents to CPA review, labelled for what it is.