FOR TAX PROFESSIONALS|FIND A TAX PROFESSIONAL
taxscout.ai
Book a Demo

Integration / CCH Axcess

TaxScout and CCH Axcess: what we can honestly say today.

You already license CCH Axcess, your staff know it, and your e-file runs through it. Nothing about adopting a workflow platform should put that at risk.

We are validating a controlled TaxScout-to-CCH Axcess handoff with design partners. Calculation and e-file stay in CCH Axcess. We publish the exact mechanism and the exact gaps rather than a logo and the word "integration".

01/Division of labour

What TaxScout handles, and what stays in CCH Axcess.

TaxScout

  • Collect — Portal, intake, documents, reminders.
  • Prepare — Document processing, workpapers, research, prior year.
  • Review — Exceptions, source links, validation, decisions.
  • Deliver — Handoff, signature, communication, billing, archive.

CCH Axcess

  • Calculation — every computed figure on the return
  • Diagnostics— the engine's own validation
  • E-file — transmission under your EFIN
  • Your licence — unchanged. We are not asking you to replace it

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.

02/Current status

The integration registry for this engine.

Statusvalidation
Mechanismstructured import
Vendor-supported mechanismNot yet confirmed
Vendor terms reviewedNot yet reviewed
Supported return typesEstablished during validation
Round-trip testedNo
Engine diagnostics returnedNo
Tested byNot yet tested
Last tested—
Version tested—
Validation partnerOpen — we are looking for one

Two of those rows are unanswered, and they are the two that matter most. Until the mechanism is confirmed as vendor-supported and the vendor terms have been reviewed, this stays in design-partner validation and is not described as a shipped integration.

03/What validation involves

What we are asking a design partner to do.

  • One real, redacted, or synthetic return — your choice, and it never has to be a live client file.
  • A licensed environment of the engine, because we will not test against an unlicensed copy.
  • One session to run the handoff and record what actually imports.
  • A second session to check the engine's diagnostics against what TaxScout sent.
  • Nothing changes about how your firm e-files during any of this.
  • We publish the result, including the parts that did not work.

04/Other engines

Where every other engine stands.

Drake SoftwareDesign-partner validation

We are validating a controlled TaxScout-to-Drake handoff with design partners. Calculation and e-file stay in Drake.

UltraTax CSWorkflow-compatible

Run TaxScout alongside UltraTax CS; hand off documents, workpapers and generic exports.

LacerteWorkflow-compatible

Run TaxScout alongside Lacerte; hand off documents, workpapers and generic exports.

ProConnectWorkflow-compatible

Run TaxScout alongside ProConnect; hand off documents, workpapers and generic exports.

ProSeriesWorkflow-compatible

Run TaxScout alongside ProSeries; hand off documents, workpapers and generic exports.

·/Limitations

What this does not do today.

  • TaxScout produces a structured export shaped for CCH Axcess import. Whether that path is vendor-supported for the current version has not been confirmed.
  • No round-trip test has been run, and no version has been recorded as tested.
  • CCH's terms have not yet been reviewed for this mechanism.
Validate CCH Axcess with us

Would you help validate a controlled TaxScout-to-CCH Axcess handoff on a real, redacted, or synthetic return?