# ProConnect Tax Online API Evaluation — SavingsMax Phase II Prep Engine Gate (Round 2)

**Author:** Riv (Integrations Specialist)
**Date:** 2026-05-23
**Recipient:** Jimmie (primary) → Rex / Atlas (downstream)
**Parent docs:**
- Ledger 2026-05-05 — SavingsMax planning scope
- Rex 2026-05-23 — SavingsMax Phase II prep addendum
- Riv 2026-05-23 — Aiwyn Tax MCP Evaluation (Round 1, no-go)
**Time spent:** ~1.5 hr desk research (no MCP for ProConnect in this environment — was always going to be web research, not hands-on probing)

---

## Executive recommendation

**❌ ProConnect Tax Online has no API. Eval surfaced a better option: ✅ CCH Axcess Tax (Wolters Kluwer).**

The headline finding pivots from the original brief. ProConnect was a dead end before I started typing, but the adjacent-landscape sweep landed on a real answer: **CCH Axcess Tax Essentials + the Open Integration Platform**. It has the right API capability *and* a small-firm SKU explicitly priced for J2's scale.

**Recommended next step (commercial, not technical):** schedule a Wolters Kluwer sales call to qualify CCH Axcess Tax Essentials pricing for J2's specific volume + Integration Vendor Program enrollment for API access. This is a 30-minute conversation with their sales team, not another technical eval.

**If CCH Axcess pricing/terms turn out wrong:** fall back to **Drake Tax Online** (the SMB market leader, marketing claims developer API support in their 2026 release — but the actual API surface is unverified and needs hands-on probing if we go that direction).

---

## 1. ProConnect Tax Online — confirmed no-go

### The headline
ProConnect Tax Online has **no public API.** Not "partner-gated" — actually doesn't exist.

### Evidence
- Intuit Accountants community **idea exchange request "API for ProConnect Tax Online"** was opened **December 2, 2022**
- Last Intuit staff response (July 7, 2023): *"The idea to implement API for ProConnect is currently Under review and the team is researching next steps"*
- **Current status of the idea: "Closed"** — 54 votes, 17 user comments, no API delivered, request now closed without resolution
- Multiple developer-help threads at `help.developer.intuit.com` confirm "no public web API for ProConnect Tax"
- Intuit's only Tax-product programmatic surface is the **Lacerte SDK** (see §2)

### What the community wanted (matches our use case)
Users requesting the API listed exactly the integrations we'd want:
- SurePrep, GruntWorx, Tallyfor, Once (these existing third-party tools already integrate with Lacerte/ProSeries via the Lacerte SDK — but Intuit chose to leave their cloud product, ProConnect, without an equivalent surface)
- Workflow automation (review, e-signatures, e-file)
- Salesforce / Microsoft / QBO data flow

This is not a niche request that Intuit hasn't seen. It's a deliberate product decision: ProConnect doesn't open up.

### Why Intuit might keep it closed
Reasonable inference: ProConnect competes with TurboTax adjacent up-market. Intuit's monetization model is per-return licensing inside their walled UI. An open API would invite white-label competitors (exactly the SavingsMax thesis) eating into their per-return margin. Closed API protects the franchise. Don't expect this to change.

### Outcome
**Cross ProConnect off the list. Don't waste another cycle on it.**

---

## 2. Lacerte SDK — desktop, wrong architecture

Intuit's only Tax-product programmatic surface is the **Lacerte SDK** (`developer.intuit.com/app/developer/lacerte-sdk`). I couldn't extract substantive content from the docs page (thin page response), but from general industry knowledge plus the community context:

- **Lacerte** is Intuit's high-end **desktop** tax product (predates ProConnect; targets larger CPA firms)
- The SDK is **COM/database-level access** to a local Lacerte installation — used by SurePrep, GruntWorx, etc. to extract source documents into Lacerte's data files
- It is NOT a cloud REST API. It requires Lacerte installed on Windows, sometimes in a hosted environment ("Lacerte Hosting" is Intuit's RDP-hosted Lacerte service)
- Even in a hosted environment, you'd be automating a Windows desktop application via COM/database — fragile, slow, and architecturally wrong for the books-to-prep continuous-loop thesis

**Lacerte license + SDK + Lacerte Hosting** is a path Rex didn't consider in his Option C/D, but I don't recommend it — the architecture mismatch is fundamental, the cost is higher than Drake/ProConnect (Lacerte targets larger firms), and the automation surface is brittle compared to a real REST API.

Cross Lacerte off too.

---

## 3. ✅ CCH Axcess Tax — the actual answer

This is Wolters Kluwer's cloud tax product. WK is the other major player in the professional tax software space (alongside Intuit and Thomson Reuters). CCH Axcess Tax replaced their legacy ProSystem fx Tax desktop and is built cloud-native.

### API capability — confirmed present
Per the **CCH Axcess Open Integration Platform** documentation:
- ✅ "Creating and managing returns for new and existing clients"
- ✅ "Importing tax data from external sources such as Excel, databases, and OCR solutions"
- ✅ "Managing electronic filing, release, and extension filing workflows"
- ✅ "Monitoring e-file status and history"
- ✅ "Retrieving and managing returns in bulk based on defined criteria"
- ✅ "Extracting return data to support review, analytics, reporting, and reuse"
- ✅ **OAuth authentication** confirmed

This is the **full return lifecycle exposed via API** — create, populate, calculate, e-file, monitor, extract. That's exactly the surface SavingsMax Phase II needs.

### Form coverage — assumed full
The CCH Axcess Tax product itself supports **the full federal and multi-state form library** including 1040, 1120-S, 1065, 1120, 1041, 990, plus all state equivalents and PTE workflows. Wolters Kluwer's tax content is one of the two industry-standard libraries (the other being Intuit's). API form-coverage detail was not exposed publicly — but the underlying product covers everything we need.

### Pricing — fits J2 (this surprised me)
**CCH Axcess Tax Essentials** is the small-firm SKU, explicitly marketed as: *"configured and designed specifically for small tax and accounting firms with four or less full-time tax professionals."*

Public pricing:
| SKU | Annual cost | Returns | States |
|-----|-------------|---------|--------|
| Essentials 100 + 5 states | $2,299 | 100 | 5 |
| Essentials 100 + unlimited states | $2,759 | 100 | unlimited |
| Essentials unlimited returns | $9,999 | unlimited | unlimited |
| Additional state | $49.95 each | — | — |

User licenses: 1–9 included in package.

**J2 projection:** 40 clients × ~2 returns each (entity + owner 1040, sometimes more) ≈ 80–100 returns/yr in steady state. **The $2,299–$2,759 tier fits today.** Growth past 200 returns/yr pushes us to the $9,999 unlimited tier — still cheap on a per-return basis.

This is dramatically more accessible than I expected. CCH Axcess (full) typically runs $20K+/yr for mid-size firms. The Essentials SKU is the small-firm answer and J2 sits squarely in its target.

### Integration Vendor Program — the API access gate
API access goes through the **CCH Axcess Integration Vendor Program**, three tiers:

| Tier | Purpose |
|------|---------|
| **Licensed Consultant** | Entry tier — "integrators that want to try the API data for testing purposes or consultants who need access to CCH Axcess to build custom integrations" — **this is the tier J2 wants** |
| Licensed Integrator Partner | Resell rights — not relevant for J2 (we're not white-labeling CCH for other firms) |
| Software Partner | Deeper integration support — for vendors like SurePrep building products on top of CCH |

**Open questions to take to the sales call (commercial, not technical):**
1. Does the Licensed Consultant tier carry a separate annual fee or is it bundled into a CCH Axcess Tax license?
2. What's the vetting process — is approval automatic for a firm licensing CCH Axcess Tax, or is there an application review?
3. Does the API surface (creation, calculation, e-file) require Licensed Consultant tier or is it included with a vanilla CCH Axcess Tax customer login?
4. What's the rate-limit / quota structure on API calls — per-firm or per-return?

The developer portal at `developers.cchaxcess.com` is **gated behind authenticated WK/CCH credentials** — I cannot self-serve probe the actual API surface without an account. Hence the recommendation to engage commercially first.

### What CCH Axcess buys J2 strategically
- **One engine for entity returns + owner 1040s + states** — the unified architecture Rex was hoping for
- **Industry-grade form library** — no maintenance burden for annual rule updates (WK does it)
- **E-file included** — IRS-certified MeF transmitter operated by WK
- **Audit-defensible work product** — CCH Axcess output is the work product top-50 CPA firms file every day; no preparer-grade-vs-estimator-grade question (the Column/Aiwyn issue)
- **Per-return economics work** — $23-28/return at Essentials tier, vs. Aiwyn's unknown commercial pricing or Drake's $1,800/yr unlimited

### What it doesn't buy
- **The "moat" is partial** — anyone willing to pay CCH could do the same integration. The J2-specific moat collapses back to the books-continuity (we own the GL, we feed CCH automatically) rather than the engine being unique.
- **Vendor lock-in to WK** — if they hike Essentials pricing or change API terms, J2 has limited recourse. Same risk as any SaaS dependency.

---

## 4. UltraTax CS (Thomson Reuters) — not an API, file-based only

Thomson Reuters' UltraTax CS integrates with their Onvio practice-management cloud and other CS Suite products, but the integration model is **file-based data sharing + status sync**, not a programmatic REST API for return creation:

- "Onvio Link" — local file-location sharing between UltraTax CS and Onvio
- Push-style sends of completed returns to Onvio Documents
- Trial balance import from Onvio Workpapers

No evidence of a public REST API for programmatic return creation, calculation, or submission. Likely partner-tier APIs exist (SurePrep integrates with UltraTax) but not publicly advertised. **Pass.**

---

## 5. Drake Tax Online — soft secondary

Drake is the SMB market leader (~70K firms, mostly solo and small practices — directly J2's size). They've moved Drake Tax to a browser-based cloud product called **Drake Tax Online**. Recent (2026) updates marketing claims include:
- "More helpful for firms using custom tools" — softer language
- "Drake Tax offers API integration that connects with third-party systems"
- Integrations listed: TaxDome, Soraban, StanfordTax, Cloud 9

**Concern:** the "API" language in Drake's marketing is suspiciously vague. Documented integrations are all practice-management / data-import partnerships (TaxDome syncs client data, StanfordTax imports prior-year returns) — not custom-developer API access. The 2026 release notes mention "improved compatibility" rather than "new public API." I'd guess Drake has a limited partner API but it's not self-serve documented, and the form-creation/calculation surface may not be exposed at all.

**Drake pricing for context:** $345 + per-return at the entry tier, ~$1,800/yr for unlimited. Cheaper than CCH Axcess but with less verified API.

**Recommendation:** keep Drake as the soft fallback if CCH Axcess commercial terms don't work. Probing Drake's API would require a Drake account + sales conversation similar to CCH.

---

## 6. The honest commercial picture

I want to flag what's changed in the architectural conversation since Rex's original addendum:

**Rex's Option B was "ProConnect Tax Online API."** That option doesn't exist. **The actual viable Option B is CCH Axcess Tax + OIP.** It's still a "buy the engine, build the workflow on top" model — exactly the architecture Rex framed — just with a different vendor.

**Rex's Option D was "TaxDome + Drake/UltraTax."** This option still exists as fallback but with the same architectural compromise Rex noted: the prep engine becomes a thin wrapper, J2 loses some workflow control. **The CCH Axcess path is better than this if commercial terms work.**

**The J2 moat changes shape:**
- Before: "we have a unique prep engine no one else has"
- After: "we have CCH Axcess like any other firm, but the books-to-CCH continuous-loop integration is unique because nobody else owns the books for these clients with the same fidelity"
- This is still a real moat — the books-side advantage is the actual moat, not the engine itself. The engine was always going to be undifferentiated capability.

---

## 7. Recommendation + next steps

### Status
✅ **Recommendation: CCH Axcess Tax Essentials + Integration Vendor Program**

### Action sequence
1. **Jimmie + Larry — schedule a 30-min sales call with Wolters Kluwer** on CCH Axcess Tax Essentials. The four open commercial questions in §3 above are the agenda. Ask specifically about Licensed Consultant API tier inclusion or separate cost.
2. **If commercial terms land cleanly:** Atlas can begin schema integration design against the OIP API contract (Wolters Kluwer publishes OAuth flow + Swagger to portal-authenticated users). Riv (me) handles the OAuth + endpoint integration once we have credentials. Estimated 2–3 weeks to a working "create entity return → populate from QBO trial balance → calculate → return PDF" demo path on a single pilot client (Afton Electric).
3. **If commercial terms don't work** (e.g. Licensed Consultant tier requires Software Partner-level commitment, or per-API-call fees are prohibitive at our volume): escalate to **Drake Tax Online sales conversation** to probe their actual API surface. Time-box another 1–2 day eval.
4. **If both Drake and CCH close out:** fall back to **Rex's Option D (TaxDome + Drake/UltraTax)** — the SavingsMax Phase II "moat" thesis weakens but the product still ships.

### What I'm NOT recommending
- Don't engage Lacerte SDK — desktop architecture is wrong for this build, regardless of credential/license cost.
- Don't wait for the ProConnect API to materialize — Intuit closed the request without delivering. Multi-year wait at best.
- Don't engage UltraTax CS — file-based integration only, no programmatic prep API.

### What this means for Atlas's schema work
Atlas should **continue to design the SavingsMax schema vendor-agnostic** for now (the planning side, per Ledger's Section 2-7, doesn't depend on which prep engine we pick). The prep-side schema additions Rex outlined in his §7 (`tax_engagement`, `tax_return`, `tax_document`, `tax_review_queue`, `tax_projection_snapshot`, `irs_authorization`, `tax_notice`) are all engine-agnostic. The CCH-specific work begins once we have the OIP contract in hand from the sales call.

---

**End of evaluation.** ProConnect closed, CCH Axcess emerged as the answer. Recommend dispatching Larry to schedule the Wolters Kluwer sales call.

Sources:
- [API for ProConnect Tax Online — Intuit Accountants Community Idea Exchange](https://accountants.intuit.com/community/proconnect-tax-idea-exchange/api-for-proconnect-tax-online/idi-p/235770)
- [Is there a public web API for ProConnect Tax? — Intuit Developer Help](https://help.developer.intuit.com/s/question/0D54R00009CYIKeSAP/is-there-a-public-web-api-for-proconnect-tax)
- [Lacerte Software Developer's Kit (SDK)](https://developer.intuit.com/app/developer/lacerte-sdk/docs/lacerte-get-started)
- [CCH Axcess Open Integration Platform — Wolters Kluwer](https://www.wolterskluwer.com/en/solutions/cch-axcess/open-integration)
- [CCH Axcess Integration Vendor Program — Wolters Kluwer](https://www.wolterskluwer.com/en/solutions/cch-axcess/vendor-program)
- [CCH Axcess Developer Portal](https://developers.cchaxcess.com/)
- [CCH Axcess Tax Essentials Packages — Wolters Kluwer](https://www.wolterskluwer.com/en/solutions/cch-axcess/tax/essentials/packages)
- [Drake Tax Online — Drake Software](https://www.drakesoftware.com/products/drake-tax-online/)
- [UltraTax CS Integration with Onvio — Thomson Reuters](https://www.thomsonreuters.com/en-us/help/onvio/common/ut-integration)